About
Claude Resets is a manually curated, independent record of public announcements about Claude usage-limit resets. It is not affiliated with or endorsed by Anthropic.
Who runs this tracker
Mike maintains Claude Resets as an independent project. The archive, filters, and history calculations are built from public evidence; this site has no access to your Claude account and cannot change your limits.
Use the limit troubleshooter and private reset-time planner when you need to work out what to do next, or read the analysis of the verified history to understand what the announcement data can tell you.
Editorial corrections
To report a missing announcement or a mistake, contact Mike with a public source URL, the affected page, and what needs changing. An account-specific reset timer is not evidence of a public reset. Corrections are recorded on event pages; additional posts about the same event are attached as sources rather than counted as extra resets.
What counts as a reset
The board counts verified resets publicly announced by official sources or Anthropic team members, labeled Banked reset or Applied reset. A banked reset is saved for the subscriber to use later. Temporary limit increases, API credits, policy changes, service incidents, and normal scheduled allowance refreshes are not counted as resets.
Does this change my account?
No. This site only records public announcements. It cannot reset, extend, or read your usage. Check your own limits inside Claude.
Availability varies by plan
Many resets are announced for all users, but some are limited to specific plans or to users affected by an issue. Each event shows the audience exactly as stated; unknown eligibility is shown as unknown, not assumed.
Subscription usage and the API
Claude subscription usage is shared across the Claude apps and Claude Code. API usage is billed and rate-limited separately and replenishes on its own schedule. Announced resets here concern subscription limits unless stated otherwise.
How the statistics work
The board total includes both applied and banked resets; several posts about one reset are merged. Average interval and longest wait measure applied resets only, using gaps between consecutive events with exact announcement times. A gap is never measured across a date-only applied reset. The latest card shows the newest reset announcement, whether banked or applied. Past gaps do not predict the next reset.
Coverage
Coverage starts on April 16, 2026, when the @ClaudeDevs account joined X. Announcements made earlier or only on other channels are outside documented coverage and are not claimed as “no reset”.
Sources and verification
Every event links to its public source posts. Post text and authorship are checked through X’s public embed data, and exact times are decoded from post IDs. Relays by team members are recorded as relays, not as separate events.
Alerts
Browser alerts (when enabled here), the Telegram channel (when one is linked) and the feeds only carry verified resets after they are published. Discovering announcements and posting to X stay manual.
Corrections
Events can be corrected or retracted. A retracted event stays visible with its reason but drops out of the count. Routine wording edits are silent.