Shaduf.Research preview
AI Model Degradation Watch/OpenAI canceled the Pro 200 usage cut; public tests still show no broad model decline
OpenAI canceled the Pro 200 usage cut; public tests still show no broad model decline — AI Model Degradation Watch

AI Model Degradation Watch · Question revision 1
Exact question: Are popular AI models getting worse right now, and what evidence distinguishes real capability degradation from outages, routing changes, product changes, safety behavior, pricing, access limits, and anecdotes?

Research review · 30 October 2026 · checked 12:07 UTC

OpenAI canceled the Pro 200 usage cut; public tests still show no broad model decline.

OpenAI canceled its planned Pro 200 Work and Codex allowance reduction on 29 October, one day before the announced cutoff. Public tests checked today do not establish a broad capability decline. They do surface narrower evidence: a resolved GPT-6.1 Sol API performance incident and an ABIS behavior-change signal for Gemini 3.5 Flash.

Reader check: Do not rely on the September allowance notice. OpenAI’s 29 October release notes cancel the Pro 200 Work/Codex reduction. Check Settings → Usage for your own plan and model before treating a quota limit as a model-quality change.

What repeated tests show

SourceLatest displayed resultScope and limit
AI Stupid LevelIts page snapshot is dated 30 October, 03:26 UTC: none of 25 models was below its recent baseline on the 24-hour boards; no detector fired among 66 armed suites. Nine of 75 suites are not yet armed.The operator describes API-side coding, reasoning and tool-use tasks. Tasks are private, so this review could not reproduce them. The board is not a test of ChatGPT, Claude or Gemini consumer-app workflows.
LiveNerf: Claude Opus 5.5Its 21–30-day window, starting 14 October, reports 780 samples, a score of 0.571 ± 0.035, and a baseline change of −0.015 ± 0.018 over 78 calibrated items. The project labels the result “no change.”The project uses a pinned Claude Code CLI with a Claude Max subscription and a fixed panel. It is a scoped, longitudinal check, not a test of every Claude surface, task, or account.
ABIS findingsABIS labels a 27 October Gemini 3.5 Flash result a “possible version update signal.” It reports drift down 73.4% and coherence up 16.0%; an earlier 17 October signal moved in the opposite direction.This is a behavioral-shift alert, not a finding of lower task capability. The public page does not identify the serving route or provider build responsible.

A confirmed service event is not a trend

OpenAI’s status record lists “6.1 Sol Degraded Model Performance” on 27 October for the Chat Completions, Responses, and Batch API components. The record says the issue was resolved after a mitigation. It confirms a narrow provider-declared API event; it does not publish a root cause, task-quality measure, or individual-account outcome.

The Pro 200 change did not happen as announced

OpenAI’s 29 October release notes cancel the Pro 200 allowance reduction announced in September. Pro 200 subscribers who already had the higher Work/Codex allowance keep it; subscribers on the lower allowance receive twice their prior allowance, bringing them to the same limit. Pro 100 and Pro 500 Work/Codex allowances also doubled. The Pro tiers help page says Pro 200 remains $200 per month. These are access changes, not evidence of a capability shift. OpenAI says the allowance does not correspond to a fixed number of messages or tasks; model, task, and settings affect how much work it covers.

What users report

A 26 October r/ChatGPTcomplaints thread asks whether GPT-6 improved conversational quality. Some comments report an unwanted sarcastic tone or weak continuity; others say GPT-6 infers intent better than GPT-5.6. These reports identify a separate task dimension—conversation quality—but do not include matched prompts, verified model receipts, or a representative sample. A new Chinese-language V2EX discussion about the allowance reversal shows that readers are still sorting out who receives a doubled allowance and who simply avoids a cut. Its 13 replies are a small thread, not a measure of demand.

Next check

For a blocked or quota-limited request, save the error, plan, model, surface, and Settings → Usage display; check the provider’s current policy and status record. For a completed answer that missed a recurring task, replay a safe task on the same surface with the same selected model, effort, context, and settings. Score task correctness, conversational fit, completion, time, and allowance separately.

See current evidence lanes · Read the assessment method · See community reports · Return to the current answer

Search published pools, pages, reports, and evidence.