Claude Getting Dumber, GPT Getting Throttled: What's Happening with AI Providers?
In April 2026, Claude showed significant quality degradation and a major outage, while OpenAI adjusted ChatGPT Pro pricing and rate limiting. What's behind it all?
Claude Getting Dumber, GPT Getting Throttled: What's Happening with AI Providers?
You've probably noticed too
If you've been coding with AI lately, you might have noticed Claude feeling less sharp, or GPT running out of quota faster than before. It's not your imagination.
In April 2026, both issues blew up simultaneously — and neither is small.
Claude: From Developer Darling to Public Enemy
Quality cliff dive
Between April 9th and 10th, numerous Claude Code users reported a sudden degradation in reasoning quality:
- Simple bug fixes: What took 1-2 attempts now requires 7-10 rounds of trial and error
- Stopped using specialized tools: The model started ignoring
/plan,/bugcommands, and no longer routed correctly to subagents - Shallower reasoning: Responses became more surface-level, lacking deep analysis
A GitHub issue (#46143) documented this change in detail — no client update, no config change, just suddenly dumber.
Even Claude admits it
The Register ran an interesting experiment: they asked Claude to analyze quality complaints in its own GitHub repo. The results:
- Jan-Feb: ~5 quality complaints per month on average
- March: Surged to 18 (a 3.5× jump)
- First 13 days of April: Already 20+, on track to exceed March
The bigger event: AMD executive's data report
On April 2nd, Stella Laurenzo, Senior Director of AMD's AI Group, filed what might be the most data-rich bug report in AI history on Anthropic's GitHub:
- Analyzed 6,852 session files
- Counted 234,760 tool calls
- Found reads-per-edit dropped from 6.6x to 2.0x
That's a drop of nearly 70%. A product's core metric losing 70% in a week would be unacceptable in any industry.
Translation: Claude stopped "reading code" before modifying it — edit without reading, introduce bugs, try again, repeat.
Anthropic's confirmed changes
- March 3: Default effort level changed from high to medium
- Feb 9: Adaptive thinking shipped, but thinking token UI display may have been hidden
- March 26: Peak-hour throttling introduced, reducing available tokens within 5-hour sessions
- Prompt cache TTL bug: Causing cost inflation of 10-20×
In short: Anthropic lowered the model's "effort level" to manage costs and cope with compute constraints. What users perceive is "it got dumber."
April 13th major outage
Adding insult to injury, Claude suffered a major outage on April 13th, affecting both Claude.ai and Claude Code for approximately 48 minutes, further fueling user frustration.
OpenAI: Price cuts + rate limiting
ChatGPT Pro price halved
On April 10th, OpenAI announced ChatGPT Pro dropping from $200/month to $100/month. Sounds great on the surface, but the underlying logic is worth examining:
- Price cuts usually mean user growth is below expectations, or the cost structure has shifted
- Simultaneously launched GPT-5.4 mini as a fallback model — automatically downgrading when rate limits are hit
Invisible quota reduction
While the price dropped, many users report tighter limits:
- GPT-5.4 Thinking usage restrictions are stricter
- More frequent fallbacks to GPT-5.4 mini
- Manual Thinking mode has a hard cap of 3,000 requests/week
The cost of lower prices is more aggressive throttling and model downgrades.
What's really going on?
Compute bottleneck is the core issue
Both companies' behavior points to the same conclusion: AI compute supply and demand are severely imbalanced.
- Explosive demand growth: AI coding tools (Claude Code, Codex, Cursor, etc.) saw explosive user growth in Q1 2026, with enterprise users flooding in
- Supply can't keep up: GPU capacity expansion takes time — new datacenter build cycles are typically 12-18 months
- Massive cost pressure: Inference costs for large models remain high, and price wars are amplifying losses
Provider strategies compared
| Strategy | Anthropic | OpenAI |
|---|---|---|
| Lower model "effort" | ✅ Default effort → medium | ❌ |
| Peak-hour throttling | ✅ Elastic 5-hour session definition | ✅ More frequent fallbacks |
| Small model fallback | ❌ | ✅ GPT-5.4 mini |
| Direct price cuts | ❌ | ✅ Pro -50% |
| Outages | ✅ April 13 major outage | — |
It's all the same playbook: when compute is insufficient, use every lever to reduce per-user resource consumption.
What this means for users
- AI coding tool costs are no longer "negligible." My 150M tokens last week (with RTK) was already compressed. Without optimization tools, costs would be much higher
- Model quality may continue to fluctuate. Providers prioritize enterprise customers when compute is scarce — individual user experience may suffer
- Tooling matters more than ever. Token compression tools like RTK have gone from "nice to have" to "must have." Multi-model strategies make more sense too
- Small models have their moment. GPT-5.4 mini shows providers are serious about "good enough" models that may be more cost-effective for specific use cases
My playbook
As a heavy AI coding user, here's my current strategy:
- RTK always on: Validated 57% token savings with zero learning curve
- Multi-model mixing: Don't rely on a single model — if Claude struggles, switch to GPT, and vice versa
- Off-peak usage: Anthropic themselves said off-peak hours offer better experience
- Local-first for simple tasks: Reserve big model quotas for complex work
The real problem: opacity
A compute shortage is understandable. What actually frustrated users was how it was handled.
Anthropic never candidly said "we're compute-constrained and need temporary throttling" — instead the default effort was quietly lowered, thinking token display was hidden, and throttling was packaged as "elastic definitions." OpenAI announced a price cut while silently switching users to the mini fallback model more often, without clear notice. You pay the same money and may receive a downgraded service, with no way to notice.
Users aren't stupid. They know exactly what they're getting and what they aren't. Instead of investing in spin, invest in capacity — give users the best product, not the cheapest excuse.
Final thoughts
The AI industry is in an interesting phase: technical capabilities are advancing rapidly, but infrastructure hasn't caught up. Providers are struggling to balance user growth, cost control, and experience quality.
For developers, the best response isn't complaining about dumber models — it's building a workflow that doesn't depend on a single provider. After all, tools exist to serve us, not the other way around.
Related posts: