Anthropic Claude reset tracker
Coverage since 2026-04-16· Sources fresh
Latest reset announcement
Latest verified full-reset announcement
(your time)
Full resetVerifiedScope stated by sourceWe've reset 5-hour and weekly rate limits for all users.
Most recent event (not a reset)
(your time)
Temporary limit boostVerifiedWe’re extending the 50% increase to weekly Claude Code limits through August 31.
Statistics
- Confirmed reset records
- 10Only verified/official hard-reset announcements count
- Average announcement gap
- 10.0days
- Longest announcement gap
- 22.0days
- Events in 26 weeks
- 14
4 event(s) excluded from interval statistics: 2 temporary multiplier, 2 quota policy change. See methodology.
Reset rhythm
2026-049 gaps2026-07
| Announcement date | Days since previous announcement |
|---|---|
| 2026-04-23 | 6.9 |
| 2026-05-15 | 22 |
| 2026-06-01 | 17 |
| 2026-06-09 | 8.2 |
| 2026-06-19 | 9.2 |
| 2026-06-20 | 0.9 |
| 2026-07-01 | 11.9 |
| 2026-07-09 | 7.9 |
| 2026-07-16 | 6.4 |
| Date | Events | Types |
|---|---|---|
| 2026-04-16 | 1 | 1 hard reset |
| 2026-04-23 | 1 | 1 hard reset |
| 2026-05-06 | 1 | 1 quota policy change |
| 2026-05-15 | 1 | 1 hard reset |
| 2026-06-01 | 1 | 1 hard reset |
| 2026-06-09 | 1 | 1 hard reset |
| 2026-06-19 | 1 | 1 hard reset |
| 2026-06-20 | 1 | 1 hard reset |
| 2026-07-01 | 1 | 1 hard reset |
| 2026-07-02 | 1 | 1 quota policy change |
| 2026-07-09 | 1 | 1 hard reset |
| 2026-07-16 | 1 | 1 hard reset |
| 2026-07-18 | 1 | 1 temporary multiplier |
| 2026-08-18 | 1 | 1 temporary multiplier |
Usage windows
- 5-hour session window
- session · anchor rolling · 5h window — Claude and Claude Code may share plan limits
- Weekly limit
- weekly · anchor account_assigned
These are normal reset rules, not events. They are tracked separately from reset events so that scheduled behaviour never appears in reset statistics.
Event archive
2 temporary multiplier · 10 hard reset · 2 quota policy change
- BoostClaude: Temporary limit increaseWe’re extending the 50% increase to weekly Claude Code limits through August 31.
- BoostClaude: Temporary limit increaseWe're also keeping Claude Code weekly limits 50% higher, now through August 19, for all Pro, Max, Team, and seat-based Enterprise users.
- Full resetClaude: Usage limits resetWe've reset 5-hour and weekly rate limits for all users.
- Full resetClaude: Usage limits resetWe've reset 5-hour and weekly rate limits for all users.
- PolicyClaude: Limit policy changedWe've raised Claude Platform API rate limits for all users and simplified the tiers, which are no longer based on API spend.
- Full resetClaude: Usage limits resetNow that Fable 5 is ready to build (again), we've reset everyone's 5-hour and weekly rate limits.
- Full resetClaude: Usage limits resetUpdate: we've gone ahead and reset 5-hour and weekly usage limits for everyone, across all plans.
- Full resetClaude: Usage limits resetEarlier 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.
- Full resetClaude: Usage limits resetWe've reset 5-hour and weekly rate limits for all users.
- Full resetClaude: Usage limits resetWe've reset 5-hour and weekly rate limits for all users on Pro and Max plans.
- Full resetClaude: Usage limits resetHappy Friday! We've reset everyone's 5-hour and weekly rate limits.
- PolicyClaude: Limit policy changedUsage limits are up, effective today we're: 1) Doubling Claude Code's 5-hour limits for Pro, Max, Team and seat-based Enterprise plans
- Full resetClaude: Usage limits resetWe 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.
- Full resetClaude: Usage limits resetWe 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.
Coverage
The monitored announcement account was created in 2026-02. Events before that date are not expected to exist.
