HOW THE RECORD WORKS

Trust the definition, then the data.

Our job is to answer what changed, for whom, and how sure we are. Every record is source-linked, and incomplete evidence remains visible rather than being promoted to a reset.

Events in record243All event types

Counted resets66Completed and confirmed

Reported resets25Completion not confirmed

Unverified7Historical leads, not facts

Event taxonomy

What counts as a reset?

Automatic reset

The provider clears a usage counter for a defined audience. The 66 dashboard resets are `global_reset` events with completed lifecycle, confirmed evidence and at least a day-precise date. Announcements without completion do not count.

Banked or redeemable grant

A credit or token you can apply later. It does not itself clear today's counter. Expiry and any required redemption are shown on the event page.

Limit and window changes

Changes to allowance, metering or refresh rules. They can make your quota last longer or shorter, but they are not a reset. A model launch or feature post alone is not included.

Promotions

Temporary boosts, extensions and endings. We show affected plans and dates when known. If a promotion is merely announced, its delivery remains unconfirmed until a source supports it.

Evidence standard

From post to record.

1. Discover

We watch official accounts, product documentation, changelogs and licensed discovery feeds. A third-party tracker is a lead, never our proof that an event occurred.

2. Read the original

We link to provider or staff posts and distinguish an announcement from a confirmation. Some first-party help pages change over time; archives are linked where available.

3. Define scope

Products, plans, models, regions and audience may differ. A Grok Bot reset is not automatically a Grok Build reset; an Antigravity Gemini reset is not a Gemini app reset.

4. Publish with uncertainty

An imminent reset announced by a first-party source becomes reported after 48 hours if it has not been retracted. Only a first-party post confirming completion makes the reset confirmed; headline counts include confirmed resets only. When the clear time is unavailable, we show the announcement date without inventing a delivery time.

Accountability

Corrections and credit.

Public correction log

Banked reset credit for Codex Plus, Pro and Business users at the GPT-6 Sol and Luna launch, until Oct 22. ↗2026-09-22 · lifecycle: active -> announced · Banked grant: 'We are loading a banked reset into all accounts' (progressive) plus the teasers. No 'landed' post yet; the lifecycle should become active once one appears.
Banked reset for Claude Code Pro, Max and Team users at the Opus 5.5 launch, usable until Oct 22. ↗2026-09-22 · effective_at: None -> 2026-09-22T16:44:06Z · Banked grant: 'Pro, Max, and Team users get a reset to use anytime' and 'your reset is available today in Settings -> Usage'.
GLM Coding Plan weekly quota reset for all ZCode users after the ZCode code-upload incident. ↗2026-09-22 · scope.audience: all_users -> affected_users · Press quotes 'will receive an additional weekly quota reset, which will be issued today' (future); TechBuzzChina's 'Affected users get a weekly quota reset' has no tense and a narrower scope. Nothing shows it was issued. | Policy (claude): a first-party announcement of an imminent reset, unretracted after 48h, is treated as completed with confidence 'reported'; only confirms_completion evidence makes it 'confirmed'.
Antigravity quotas reset for everyone after errors under high Gemini 3.8 Flash load. ↗2026-09-22 · effective_at: None -> 2026-09-16T05:03:03Z · 05:03 'Fixed, rolled out quota resets for everyone'; Sep 15 'will be resetting rate limits as soon as this is resolved'.
Codex usage limits reset for everyone alongside Astra quality fixes. ↗2026-09-22 · effective_at: None -> 2026-09-12T08:09:17Z · 08:09 'Reset all propagated'; 03:20 'a reset is also landing by midnight today'.
Banked reset credit for Codex users whose banked resets failed to fully apply, until Oct 9. ↗2026-09-22 · confidence: confirmed -> reported · Banked grant: 'Everyone who used one ... is getting another one and an email' (progressive); nothing confirms the re-grant landed. | Policy (claude): a first-party announcement of an imminent reset, unretracted after 48h, is treated as completed with confidence 'reported'; only confirms_completion evidence makes it 'confirmed'.
Codex usage reset for Plus, Pro and Business so users could keep using Astra before the work week. ↗2026-09-22 · effective_at: None -> 2026-09-08T04:05:53Z · 04:05 'All reset for everyone'; Sep 7 announcement 'Lands around 6pm PST today'; help center 'On September 7, 2026, we provided a global reset'. effective_at uses the confirming post as the upper bound.
Grok Bot usage limits reset for everyone again. ↗2026-09-22 · effective_at: None -> 2026-09-05T18:24:39Z · @bot 'We've reset usage limits for all Grok Bot users'; community echo.
Claude weekly limits reset for all Max users for the Fable 5.1 launch and the long weekend. ↗2026-09-22 · effective_at: None -> 2026-09-04T20:08:45Z; scope.audience: all_users -> paid · Lydia Hallie 'We've just reset weekly limits for everyone on a Claude Max plan'; daily.dev headline reports the reset.
Antigravity Gemini quotas reset for everyone amid heavy load after the Gemini 3.8 Flash launch. ↗2026-09-22 · confidence: confirmed -> reported · 'We're resetting Gemini quotas on Antigravity' (progressive); the blog note ('launch post') does not state a reset. | Policy (claude): a first-party announcement of an imminent reset, unretracted after 48h, is treated as completed with confidence 'reported'; only confirms_completion evidence makes it 'confirmed'.
Claude Code 5-hour and weekly limits reset for everyone with the Fable 5.1 launch. ↗2026-09-22 · effective_at: None -> 2026-09-01T18:35:27Z · 'we've also reset 5-hour and weekly limits for all users'.
Grok Bot token usage reset for everyone again. ↗2026-09-22 · confidence: confirmed -> reported · Musk 'We're giving all @Grok @Bot users another free reset' (progressive); no completion source. | Policy (claude): a first-party announcement of an imminent reset, unretracted after 48h, is treated as completed with confidence 'reported'; only confirms_completion evidence makes it 'confirmed'.
Banked Reset Card for every GLM Coding Plan subscriber for its first anniversary, refilling 5-hour and weekly quota. ↗2026-09-22 · effective_at: None -> 2026-09-01T12:49:29Z · Banked grant: 'we're giving every current subscriber a Reset Card. Use it to refill...', with usage links, is a present grant; the press note describes redemption mechanics.
Codex and ChatGPT Work limits reset for all paid plans at 25M active users. ↗2026-09-22 · effective_at: None -> 2026-08-31T02:29:25Z · 02:29 'we have now reset usage' (02:34 is a repost); Aug 29 'moved to tomorrow' and Aug 30 'will land at 6pm PST' are promises.
Codex and ChatGPT Work limits reset for all paid plans with usage-bug fixes giving 10–50% more usage. ↗2026-09-22 · confidence: confirmed -> reported · Staff post says only 'We are reseting usage' (progressive); the daily.dev press headline reports that OpenAI reset the limits. So completion is press-only and becomes reported. The next day's 'button was already pressed today' post also supports it, but belongs to the 25M event.
Codex and ChatGPT Work usage reset for everyone, giving brand new usage. ↗2026-09-22 · effective_at: None -> 2026-08-27T16:35:05Z · 'brand new usage for all ChatGPT Work and Codex users ... one button press at a time' states fresh usage now exists (playful, but a present-state completion).
Grok Bot opened to all SuperGrok and Cursor Pro subscribers, and weekly limits reset for all users. ↗2026-09-22 · confidence: confirmed -> reported · @bot 'We're also resetting weekly usage limits' (progressive); Musk's 'Free usage limit reset for Grok @Bot users' is a headline with no tense; the x.ai page is about the plan expansion. Nothing states completion. | Policy (claude): a first-party announcement of an imminent reset, unretracted after 48h, is treated as completed with confidence 'reported'; only confirms_completion evidence makes it 'confirmed'.
Codex usage fully reset for all paid plans alongside fixes for several usage drains. ↗2026-09-22 · effective_at: None -> 2026-08-24T00:46:51Z · 'Reset has been propagated to accounts'; Aug 23 post 'we will also do a full reset'.
Banked reset credit for Codex and ChatGPT Work paid plans at 20M active users, until Sept 21. ↗2026-09-22 · effective_at: None -> 2026-08-22T00:50:36Z · Banked grant: 'The banked reset has landed'; the earlier posts promised it 'during the day' / 'by 8pm PST'.
GLM Coding Plan 5-hour and weekly usage reset for everyone with the GLM-5.3 launch. ↗2026-09-22 · effective_at: None -> 2026-08-14T06:50:20Z · ZixuanLi 'We will soon reset'; zcode_ai '5-hour and weekly usage are back to zero' (completed state); ZixuanLi Aug 15 'The reset was completed'.

Discovery feed credits

This site publishes its own concise factual metadata and summaries. Provider posts belong to their authors.