Anthropic adjusts Claude session limits and says users will use up their limits faster during peak hours, amid compute strain due to Claude's new popularity
Follow Brent D. Griffiths … - Anthropic adjusted Claude usage caps during peak hours. — The changes show that the AI company is experiencing some compute strain.
Business InsiderBrent D. Griffiths
Context & Ripple Effects
Anthropic has already been recalibrating access as Claude’s product surface expands: restrictive Claude Code limits drew complaints from high-tier users, and the company later outlined new Pro and Max rate limits aimed at unusually continuous use. Claude Cowork’s availability to Pro subscribers also came with an explicit warning that those users could reach caps sooner.
First-order effects
Claude users face shorter effective sessions during peak periods, making access less predictable precisely when demand is highest.
Anthropic can ration constrained inference capacity through usage caps rather than offering uniformly available service at existing plan terms.
Second-order effects
Heavy Claude Code and Cowork users may need to shift work outside peak windows, reduce continuous workloads, or reassess whether a subscription tier provides dependable capacity.
The move makes capacity policy a more visible product differentiator for competing AI assistants, particularly for customers whose workflows depend on sustained availability.
Third-order effects
If recurring caps persist as products broaden, frontier-model subscriptions are likely to evolve from simple feature bundles toward explicitly managed capacity allocations by time, workload, or usage level.
This is evidence of an AI infrastructure bottleneck: service quality will depend not only on model capability but also on how providers meter scarce inference during demand spikes.
The trend: Consumer and business AI services are moving toward adaptive inference budgeting as providers balance growing usage against finite compute capacity.
To manage growing demand for Claude we're adjusting our 5 hour session limits for free/Pro/Max subs during peak hours. Your weekly limits remain unchanged. During weekdays between 5am-11am PT / 1pm-7pm GMT, you'll move through your 5-hour session limits faster than before.
We've landed a lot of efficiency wins to offset this, but ~7% of users will hit session limits they wouldn't have before, particularly for pro tiers. If you run token-intensive background jobs, shifting them to off-peak hours will stretch your session limits further.
Overall weekly limits stay the same, just how they're distributed across the week is changing. I know this was frustrating. We're continuing to invest in scaling efficiently. I'll keep you posted on progress.
Thariq: “I need to give our customers less for the same price. How can I obfuscate that as much as possible” Claude: “How about 'You'll move through your 5-hour session limits faster than before'”
Devs who can code also WITHOUT AI as well looking to became 10x more valuable They are the ones who won't panic or be idle when their Claude quota runs out... So much for all the advice on how learning to code is not worth it any more...
meanwhile, you can enjoy Codex with 2x rate limits for the next week 24x7 across all ChatGPT subscriptions! npm i -g @openai/codex time to build is NOW!!
You're going from rewarding users using it during off-peak hours (double usage which ends March 28th) to punishing them for using during peak hours. I think that's a terrible move if you want happy customers.
You make this announcement BEFORE you make the change. Good riddance... what a shame @AnthropicAI and @claudeai. Customer service isn't hard, @DarioAmodei. This was a rug pool and y'all got caught. I hope the @FTC fines you.
I think people are overreacting to this. It sucks, but they clearly have a real compute shortage and this was the best path they had without cutting your usage massively