We've just reset weekly limits for everyone on a Claude Max plan. With Fable 5.1 out and a long weekend ahead for many of you, we wanted to keep you building. I'd love to see what you build!
WHENRESET.FYI THE UNOFFICIAL RESET TRACKER
Recorded Claude reset announcements, linked to the original X posts. Announcement timestamps are separate from your personal session and weekly quota windows.
Claude · LATEST RESET ANNOUNCEMENT
52days ago
Tracked announcements12in the available history
Average interval12.8dayshistorical, not a forecast
Longest interval47.6daysbetween announcements
A little reset history
Last 26 weeks · UTCThe announcement log
With Fable 5.1 out today, we've also reset 5-hour and weekly limits for all users.
Now that Fable 5 is ready to build (again), we've reset everyone's 5-hour and weekly rate limits.
Update: we've gone ahead and reset 5-hour and weekly usage limits for everyone, across all plans. Enjoy your weekend!
Earlier today, ~3% of Claude Code Max and Pro users hit a bug that showed an incorrect weekly usage limit, and in some cases blocked them from sending messages. This is fixed, and we're resetting 5-hour and weekly limits for everyone affected. Apologies for the disruption.
We've reset 5-hour and weekly rate limits for all users on Pro and Max plans. We fixed an issue that caused some Claude Code sessions to spawn excessive parallel subagents, burning through usage faster than expected.
Over the past month, some of you reported Claude Code's quality had slipped. We investigated, and published a post-mortem on the three issues we found. All are fixed in v2.1.116+ and we’ve reset usage limits for all subscribers.
We fixed a bug where rate limits on Claude subscriptions weren't properly adjusted for long context requests in Opus 4.7. We've reset 5-hour and weekly rate limits. Enjoy Opus 4.7!
What does this Claude tracker cover?
Claude history is collected through a public feed. Routine account-window refreshes do not require a public announcement; exceptional resets and promotions need their own source evidence. The limits guide explains account usage and what to check when you reach a limit.
Sources: Claude usage and length limits
Coverage and methodology
Codex uses the Codex Resets public API; Claude uses the whenreset.dev public feed; Grok Bot includes reviewed history. Coverage may be incomplete, and secondary collection does not imply independent verification of every post.
Statistics use recorded announcements, including resets and banked credits. Scheduled entries are excluded from interval calculations. Gaps use UTC announcement timestamps, do not predict future resets and do not prove every account received a reset.