Step-by-Step Fix
1. Determine if you are experiencing throttling or a different problem
Throttling during peak hours has specific symptoms. Confirm at least two of the following apply:
- Time-of-day pattern: slowness occurs between 5 AM and 11 AM PT on weekdays but not in the evenings
- Quota depletion: your 5-hour window usage counter is dropping faster than previous sessions
- Response latency: Claude takes 15–45 seconds to return responses that normally come in 3–5 seconds
- Status page: status.anthropic.com shows all systems operational (no active incident)
If the issue occurs at all hours equally and the status page shows an incident, you are likely dealing with an outage, not throttling.
2. Shift your heavy work to off-peak hours
The single most effective throttling workaround is timing. Off-peak hours where Claude performs at its best:
- 11 PM to 5 AM PT (2 AM to 8 AM ET) — lowest global demand
- 5 AM to 7 AM PT (8 AM to 10 AM ET) — before the peak demand surge
- Weekends, early morning — Saturday and Sunday before 10 AM PT are consistently light
Peak hours to avoid for heavy tasks:
- 5 AM to 11 AM PT (8 AM to 2 PM ET, 13:00 to 19:00 GMT) — US morning work hours
If your work is in Europe, note that 13:00 to 19:00 GMT (1 PM to 7 PM in the UK) aligns with the worst US morning congestion window.
3. Understand the March–May 2026 incident
Between March and May 2026, Anthropic faced a significant throttling crisis affecting Pro and Max users. The key facts:
- Some Claude Max users reported their full 5-hour session quota exhausting in under 19 minutes during peak hours (8 AM to 2 PM ET). This was roughly 15x faster than normal session depletion.
- The throttling was worst on weekday mornings, particularly between 9 AM and 12 PM ET.
- Anthropic's load balancing was effectively treating peak-hour messages as costing 2–3x more quota than off-peak messages — a multiplier that was not publicly documented.
- This affected users on both Claude Pro and Claude Max, though Max users had more buffer before hitting the hard cap.
On May 6, 2026, Anthropic announced they had removed the peak-hour priority throttling for Pro and Max subscribers. The most severe form of accelerated quota depletion was turned off.
4. Check what is still in effect versus what was fixed
After the May 6 update, the situation changed as follows:
What was fixed (as of May 6, 2026):
- The deliberate quota-multiplier during peak hours (2–3x faster depletion) was removed for Pro and Max subscribers
- Pro and Max users should now see consistent quota consumption rates regardless of time of day
- The 19-minute session burnout issue should not occur under normal usage
What may still occur:
- General response latency during high-demand periods (slower replies, not faster quota depletion)
- Free-tier users may still experience throttling during peak hours
- Very heavy usage sessions (large documents, very long context) may still see slowdowns during extreme demand spikes
- API users on legacy plans may experience different throttling behavior than claude.ai interface users
5. Optimize your session structure to minimize throttling impact
Even outside of peak hours, session structure affects how efficiently you use your window:
- Start with a fresh conversation — carrying forward 50 previous messages adds context overhead to every subsequent message, consuming more compute per request.
- Upload documents at the start — processing a large document at the beginning of a session is more efficient than re-referencing it repeatedly mid-conversation.
- Use project contexts wisely — Claude's Projects feature (available to Pro and Max) maintains context between sessions without consuming it within a single window. For ongoing work, Projects reduce per-session overhead.
- Avoid unnecessary re-explanations — do not repeat background context in every message. Establish it once at the start of the conversation.
6. Diagnose slow responses vs. usage limit exhaustion
Slow responses and hitting your usage limit are different problems with different solutions:
Slow responses (throttling):
- Claude is still responding, just taking longer (10–45 seconds per reply)
- Your session counter shows quota remaining
- Continuing to work is fine — just slower
- Best response: wait it out or switch to off-peak hours
Usage limit hit:
- Claude stops responding and shows a wait-time message
- Your session counter shows near-zero quota
- Retrying will not help until the window resets
- Best response: wait for the 5-hour window to reset
If you are unsure which you are experiencing, send a simple short test message ("What is 2+2?"). If it responds normally in a few seconds, it is not a usage limit. If it takes 30 seconds but responds, it is throttling. If it shows an error message with a wait time, it is a usage limit.
7. Check the Anthropic status page and community channels
When you suspect throttling, two quick checks help confirm it:
- status.anthropic.com — shows real-time system status. If all indicators are green but you are experiencing slowdowns, it is load-based throttling rather than an outage.
- r/ClaudeAI on Reddit — during peak-hour congestion events, users post real-time observations. Searching "slow" or "throttling" with a time filter of "past 24 hours" quickly shows whether others are affected simultaneously.
If multiple users report the same slowdown at the same time and the status page shows no incident, Anthropic is typically aware and working on it — individual support tickets add noise but rarely accelerate the fix.
8. API users: throttling works differently than claude.ai
If you use Claude via the Anthropic API rather than the claude.ai interface, throttling operates under different rules:
- API throttling is based on tokens per minute (TPM) and requests per minute (RPM) limits tied to your API tier, not a 5-hour window.
- API users on higher tiers (Tier 3, Tier 4, Tier 5) have significantly higher TPM limits and are less likely to be throttled.
- Peak-hour slowdowns still affect API latency (response time), but the quota-multiplier throttling from the March–May 2026 incident primarily affected claude.ai interface users, not API users.
- To check your API tier and current rate limits, visit console.anthropic.com → Settings → Limits.
If you run automated workflows via the API and experience peak-hour slowdowns, consider implementing exponential backoff in your code to handle temporary 429 (rate limit) responses gracefully.
Why This Happens
Anthropic's servers face uneven demand across the day. US morning hours concentrate the highest volume of requests from both individual users and enterprise API clients. During peak demand, Anthropic's infrastructure balances load by slowing the processing rate for individual requests, which in the March–May 2026 period translated into session quotas being consumed at 2–3x the normal rate. This is a supply-demand problem: Claude's computational resources are finite, and morning hours concentrate a disproportionate share of global daily demand. The May 6 fix removed the deliberate quota-multiplier, but the underlying load pattern means some residual slowdowns during peak hours remain possible during unusually high demand events.
Common Mistakes to Avoid
- Assuming slow responses mean your account is broken — peak-hour slowdowns affect all users; they are not account-specific and do not indicate anything wrong with your subscription.
- Repeatedly sending the same message when Claude is slow — resending the same prompt during a slow period often queues multiple duplicate requests, making congestion worse and potentially accelerating quota depletion.
- Scheduling critical deadline work during peak hours — if a task must be done right and done fast, schedule it for off-peak hours. Peak hours are not reliable for time-sensitive work.
- Upgrading to Max expecting zero throttling — Max reduces how often you hit the usage cap, but before May 6, 2026, even Max users experienced peak-hour throttling. The fundamental fix was the quota-multiplier removal, not the plan tier.
- Not checking status.anthropic.com first — it takes 10 seconds and immediately tells you whether the issue is platform-wide or specific to your session timing.
- Confusing throttling with the internet connection — peak-hour Claude slowness occurs even on fast, stable connections. Running a network speed test during a Claude slowdown will show normal speeds, because the bottleneck is on Anthropic's server side, not your network.
FAQ
What are Claude's peak hours when throttling is worst? Peak throttling hours are 5 AM to 11 AM PT (8 AM to 2 PM ET, 13:00 to 19:00 GMT). This window corresponds to US morning work hours when demand is highest. During this period, Claude may respond more slowly, and your 5-hour usage window may deplete faster.
My Claude Max 5-hour session was exhausted in 19 minutes — is that a bug? This was documented throttling behavior during the March to May 2026 peak-period congestion. Anthropic's load balancing was charging each message at 2–3x the normal compute rate during peak hours. Anthropic began addressing this on May 6, 2026, by removing the peak-hour quota multiplier.
Did Anthropic fix the peak-hour throttling problem? Partially. On May 6, 2026, Anthropic removed peak-hour priority throttling for Pro and Max subscribers, eliminating the deliberate quota-multiplier effect. Some residual slowdowns may still occur during extremely high demand periods, but the severe 19-minute session burnout issue should not recur under normal usage.
How do I tell if Claude is throttling me versus having a general outage? Throttling: responses come but are slow, and status.anthropic.com shows all systems operational. Outage: requests fail entirely with errors, and the status page shows an active incident. Check the status page first — it takes 10 seconds and immediately distinguishes between the two.
What is the best time to use Claude Pro or Max for heavy tasks? 11 PM to 5 AM PT (2 AM to 8 AM ET) on weekdays, or weekend mornings before 10 AM PT. These windows have the lowest server load and the most consistent response times. Your 5-hour usage window will last its full intended duration without throttling.
Is throttling a reason to upgrade from Pro to Max? Upgrading to Claude Max gives you a higher usage cap per 5-hour window, which means throttling takes longer to push you to the limit. But upgrading does not eliminate throttling itself. The timing strategy (using off-peak hours) remains the most reliable fix regardless of plan tier.