What counts

Reading an advance warning

An announcement states the provider’s plan. An inferred hint interprets an authorized source in context. Tibo’s Codex milestone posts and replies sometimes signal a reset before a formal announcement; general excitement about a release is not enough.

Replies can add a time, move it, or correct it. We show the latest supported expectation and retain earlier timing on the event page. Clock times on the pages use your timezone; the stored record stays UTC. Passing the expected time means we are awaiting an outcome, not that the reset happened.

An automatic reset may make it useful to finish planned work with your remaining quota beforehand. A banked reset is saved to redeem later, so you do not need to spend quota before that grant. An inferred hint may not establish which kind is coming.

Subscribe to the warning feed for new warnings and timing revisions. The full record feed includes historical announcements. Telegram follows the providers you choose. Turn on hints, confirmations, or both.

Resets and grants

• Full reset: the provider clears current usage so the affected users can use their allowance again.
• Banked reset: users receive a reset they can redeem later.
• Temporary increase: the provider raises limits for a stated period.
• Usage credit: users receive additional usage without clearing the current meter.

Personal five-hour and weekly renewals, individual support credits, API billing credits, permanent plan changes, and model-access announcements are excluded.

Status

• Confirmed: the provider says the reset or grant is being issued or has been issued, or reviewed reports from separate subscribers confirm receipt of an announced grant. Receipt reports are reviewed and linked. “Reset button pressed” qualifies immediately; propagation need not be proved.
• Likely / unconfirmed: a provider announcement or an authorized representative signals a coming change. It is excluded from confirmed counts until the source confirms the reset is being issued or has been issued.
• Expired: a completed benefit has passed its stated end date.
• Retracted: the claim was withdrawn or corrected. The labeled record stays available.

An expected date comes from the source. Passing that date does not confirm a reset. If an end date has no time zone or clock time, expiry waits until that date has ended everywhere.

Sources and coverage

Checks of selected provider blogs and authorized social accounts, including replies, are scheduled every five minutes. The provider status shows when updates are delayed. A source outage or an announcement outside those feeds can cause a miss. An empty provider page means we have no qualifying records, not that the provider has never reset a quota.

Some Codex records come from a provider usage screen showing an early replenishment and a changed reset schedule. These remain personal observations and do not count as additional resets. Manual review may link receipt to a matching provider announcement to confirm issuance; it does not establish delivery to every account.

AI reads each verified source with its linked conversation context. A confirmed label requires source language saying the reset or grant is being issued or has been issued. Missing audience or timing details stay unstated. Interpretation can be wrong; the original evidence is linked for review.

History and corrections

Related announcements and confirmations count as one event when the evidence connects them. Counts include confirmed and expired events. Older unresolved warnings remain in the archive.

Event pages and API identifiers stay available after updates. Event numbers can change when records are corrected.

Email a correction with the event URL and the original source.

Who runs this

QuotaResets is operated by Luxore LLC, independently of the providers it tracks. Paid ads are labeled Sponsor; commission links are labeled Affiliate. Neither affects which events we publish.