Anthropic just quietly dropped something useful — and it expires on March 27, 2026.
They announced on X that they're doubling usage limits outside peak hours for the next two weeks. If you're using Claude Code, you've probably already seen the banner inside the app.
What's Happening
Until March 27, you get 2x your normal usage limits — but only during off-peak hours.
The peak window when limits are not doubled: 5:00 AM to 11:00 AM Pacific on weekdays.
Outside that window on weekdays, and all day on weekends, you get double the usage. Simple rule: avoid that six-hour weekday window and you're getting twice as much Claude.
By Timezone
That 5-11 AM Pacific window translates differently depending on where you are:
- US Pacific: 5:00 AM - 11:00 AM (peak). After 11 AM on weekdays is fair game.
- US Eastern: 8:00 AM - 2:00 PM (peak). Afternoons and evenings are your off-peak window.
- UK (GMT): 1:00 PM - 7:00 PM (peak). Mornings and late evenings work best.
- Central Europe (CET): 2:00 PM - 8:00 PM (peak). Mornings are your friend.
- Pakistan (PKT): 6:00 PM - 12:00 AM (peak). Mornings and early afternoons are off-peak.
Weekends are fully off-peak everywhere. No restrictions, all day, both days.
What to Do With This
Think about all the expensive, token-heavy tasks you've been putting off in Claude Code:
- Long refactors across multiple files
- Full codebase rewrites
- Generating entire features from scratch
- Running multiple agentic loops back to back
- Complex debugging sessions with Max effort
These are exactly the kinds of tasks that burn through your limits fast. This two-week window is the perfect time to tackle them.
If you've been holding back on running big tasks because you were worried about hitting limits — now is the time.
Why This Is Happening
This isn't just generosity. It's classic load balancing.
Anthropic's servers are heavily used during those peak morning hours (US business hours) and underutilized at other times. By incentivizing you to shift your usage to off-peak hours, they reduce load on their infrastructure while giving you something valuable in return.
Everyone wins.
Summary
- 2x usage limits outside 5-11 AM Pacific on weekdays
- All day on weekends = double limits
- Expires March 27, 2026
- Plan your heavy Claude Code sessions around this window
Watch the full breakdown: Claude Code Double Usage Limits — How to Maximize Before March 27
Originally published at ayyaztech.com
Top comments (1)
The fact that "maximize before the limits change" is even a genre tells you how much usage anxiety the current pricing creates - you're optimizing your work around the vendor's quota windows instead of around the actual problem. That's a tell that the cost model has the tail wagging the dog.
The escape from quota-anxiety entirely is to not be dependent on one provider's limits - go model-agnostic so the mechanical bulk of work runs on cheap/abundant models and you reserve the premium quota for what truly needs it. That's the design of Moonshift: a multi-agent pipeline (prompt to a shipped SaaS on your own GitHub + Vercel) where routing means you're never bottlenecked on a single vendor's cap, and a full build is ~$3 flat regardless of quota windows. First run's free, no card. Practical heads-up post - genuinely curious, do you find yourself rationing/timing work around these limits, or have you mostly moved heavy lifting to other models to avoid the cap dance?