What happened: variable session limits during peak hours
On 26 March 2026, Anthropic officially confirmed a change to how Claude's usage limits work. The key change: during peak hours — defined as 05:00–11:00 Pacific Time, roughly 1 PM–7 PM CET — the 5-hour session budget is consumed more quickly.
In practice, Anthropic introduced a dynamic token pricing mechanism based on demand. During traffic peaks, each interaction with Claude "costs" more in terms of session budget. This means the same volume of work that would normally take 5 hours can exhaust the limit in less time if done during the busiest time slots.
Overall weekly limits remain unchanged. Only the speed at which the session budget is consumed during peak windows has changed. Anthropic also specified that the change affects Free, Pro and Max plans, while Enterprise and API are not impacted.
Why Anthropic changed the limits: the context
To understand this decision, you need to look at what happened in the preceding weeks. In late February 2026, OpenAI announced a contract worth over $200 million with the Pentagon. The reaction was immediate: the #QuitGPT movement led over 2.5 million users to cancel their ChatGPT subscriptions, with a peak of 295% more uninstalls in a single day.
Claude was the main beneficiary of this exodus. The app went from position #42 to the number one spot on the US App Store in under a week, reaching 11 million daily active users. Anthropic found itself managing an unprecedented wave of new users, and its computing infrastructure — however robust — required rebalancing.
Anthropic CEO Dario Amodei publicly rejected Pentagon pressure to use Claude for autonomous weapons, stating that "threats do not change our position." This further fuelled the migration from ChatGPT to Claude, worsening the capacity problem.
Impact by plan: who is most affected
Not all plans are impacted equally. Here's the breakdown:
Claude Free: free-tier users already had tight limits. The change further reduces capacity during peak hours, but the practical impact is limited since the Free plan is designed for occasional use.
Claude Pro ($20/month): this is the most affected plan. About 7% of Pro users now hit limits they wouldn't have reached before. Those who use Claude intensively between 1 PM and 7 PM CET may find themselves blocked earlier than expected.
Claude Max ($100/month for 5x, $200/month for 20x): the impact is minimal. Only 2% of Max 20x users notice any difference. The Max 5x plan offers a significant buffer, and the 20x tier makes the issue essentially non-existent.
Claude Team ($25–30/month per user): the Team plan shares the same infrastructure as consumer plans but with more generous limits. The impact is moderate and manageable with workload planning.
Claude Enterprise (custom pricing): not impacted. Enterprise customers have guaranteed priority access and dedicated SLAs. This is one of the reasons why, for business-critical use, Enterprise remains the right choice.
API access: not impacted. API limits are managed separately via per-organisation rate limits and are not subject to peak-hour variations.
Want to discuss with an expert?
30 minutes to discuss your specific case.
What this means for European businesses
The peak hours defined by Anthropic (1 PM–7 PM CET) coincide with the heart of the working day in Europe. This means business teams using Claude Pro or Team during office hours are potentially the most exposed.
For companies that have adopted Claude as a daily work tool — for document analysis, content generation, legal support, financial modelling — a slowdown or block in the middle of the day can impact productivity. It's important to distinguish between occasional and structured use: a professional making 5–10 queries a day won't notice any difference, but a team using Claude intensively for consecutive hours during the afternoon could.
Companies using Claude via API for custom integrations are not affected, since API limits are independent from those of the web interface. This is yet another argument in favour of programmatic integration for critical workflows.
Practical strategies to manage the new limits
There are several strategies businesses can adopt to mitigate the impact of peak-hour limits.
Redistribute workloads: move the most intensive Claude activities (long document analysis, batch content generation, code review) to morning hours (8 AM–1 PM) or evening hours (after 7 PM), when limits are standard.
Consider a plan upgrade: if your team frequently hits limits, upgrading from Pro to Team or from Team to Enterprise eliminates or drastically reduces the problem. The detailed plan comparison helps with the decision.
Use the API for critical workflows: processes that cannot tolerate interruptions — such as automated pipelines, internal chatbots, integrations with business systems — should go through the API, which is not subject to peak-hour session limits.
Monitor team usage: with Claude Team or Enterprise, the admin panel lets you see usage patterns and identify bottlenecks before they become a problem.
Optimise interactions: using effective prompt engineering to get better responses with fewer exchanges reduces overall session budget consumption.
The bigger picture: Claude's growth and future implications
This change to limits is a sign of growth, not weakness. Claude is experiencing unprecedented expansion, driven both by model quality (Opus 4.6 and Sonnet 4.6 are among the most highly regarded on the market) and by Anthropic's ethical positioning.
For businesses, the lesson is twofold. On one hand, relying on a single AI provider carries capacity risks — it's worth having a multi-provider strategy or at least a contingency plan. On the other, dynamic limits incentivise more conscious and structured AI use, which ultimately produces better results.
Anthropic is investing heavily in infrastructure to handle growing demand. It's likely that peak-hour limits will be progressively relaxed as computing capacity increases. In the meantime, companies that adopt Claude Enterprise or integrate Claude via API are the least exposed to these fluctuations.
If your company is evaluating how to structure Claude adoption to avoid these bottlenecks, contact us for a free consultation. We help European businesses choose the right plan and configure Claude for optimal use.