Shaduf.Research preview
AI Model Degradation Watch/A live API monitor reports no broad drop; a Claude connector incident is resolved
A live API monitor reports no broad drop; a Claude connector incident is resolved — AI Model Degradation Watch

Pool topic: 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 · 29 October 2026 · checked 12:06 UTC

A live API monitor reports no broad drop; a Claude connector incident is resolved.

Call: broad capability decline remains unestablished. AI Stupid Level reports no below-baseline result among 25 models on its 24-hour API boards at 10:31 UTC. That is a current counterweight to complaints, not a test of every consumer chat surface. BridgeBench’s separate NerfBench board is older: its latest visible session is 16 October.

What to do: if a request or connected tool failed, check that component’s status record. If a completed answer missed a task, compare the same safe task on the same surface, model selection, effort, and context. Record the final result separately from quota, cost, and correction time.

What the monitors report

SourceCurrent displayScope and limit
AI Stupid LevelAs of 29 October, 10:31 UTC: none of 25 models is below its recent baseline on the 24-hour boards. The page reports zero detector flags among 66 armed model-suite detectors; nine of 75 are younger than the stated 10-day arming period.The operator says these tests use provider APIs, private tasks, and separate coding, reasoning, and tool suites. The result is not independently reproduced here and does not cover consumer app prompts, account routing, or a reader’s task.
BridgeBench NerfBenchStill dated 16 October. GPT-6 Astra: 97.1%; GPT-6.1 Sol: 98.0%; Claude Sonnet 5.5: 98.9%; Claude Opus 5.5: 105.8%. All are within the publisher’s 90–110% band. Opus rose 10.1 percentage points from 9 to 16 October.The composite combines correctness, output tokens, and cost; the public page does not show each component or task outputs. The publisher says its 50-task suite is run three times per week, but visible dates do not show that cadence. Its first tracked session is the reference, not necessarily launch performance.

Safety can move in a narrow direction

OpenAI’s October GPT-6 system card reports selected safety-evaluation regressions for GPT-6 Sol and Luna alongside improved factuality on nearly all reported difficult prompt metrics and fewer unnecessary refusals. The provider’s chosen test sets do not estimate how often typical users see these outcomes. Safety behavior should be tracked by category; it is not interchangeable with an overall capability score.

Service and model-path changes

RecordWhat it saysWhat it does not show
Anthropic Google Calendar connectorAnthropic lists elevated errors on Claude.ai, Claude Code, and Claude Cowork from 11:07 UTC on 26 October through 18:52 UTC on 28 October, then resolved.A connector failure can interrupt a task before or during tool use. It is not a rating of completed answers or proof of recovery on every account.
OpenAI GPT-6.1 Terra rolloutThe 26 October release notes say Terra is rolling out in Work and Codex; some eligible Plus/Pro Work users may see Terra at Medium instead of GPT-6.1 Sol at Light in the default Power preset.Eligibility and settings vary by account and workspace. A model/effort path change is not a matched before-and-after task test.

Users still report real task costs

A rechecked r/ChatGPT discussion contains self-reports about context, calculations, generic answers, and repeated correction, alongside comments reporting no change or good results on other tasks. A Spanish-language post reports a Chat model change, context issues, and a Work/Astra task that the author says did not progress before Claude completed it. These are useful task leads, not representative samples: neither post provides a matched task replay, verified serving receipt, or user denominator.

Reader’s next check

Save the surface, selected model, effort, context, timestamp, and completion status. For a failed connected tool, check the connector and provider status history. For a completed poor answer, rerun a safe fixed task and score correctness, safety, latency, tokens, cost, quota, and correction separately. Do not infer a model-weight change from a product rollout, service failure, or single complaint.

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

Search published pools, pages, reports, and evidence.