Research review · 31 October 2026 · checked 12:08 UTC

Gemini’s old API model name now routes to 3.6; two tracker watches remain unconfirmed.

The model label stayed familiar while the serving path changed. Google’s documentation now says requests using gemini-3.5-flash are routed to gemini-3.6-flash. That may explain why a behavior monitor saw movement, but it does not establish that quality fell.

The new route explains a label, not a score

Google’s Gemini API documentation, last updated 30 October, says gemini-3.5-flash is deprecated, no longer selectable in AI Studio, and automatically routed to gemini-3.6-flash for API requests. Google asks developers to update the model string. The page does not give an effective timestamp, account-level serving receipt, or before/after quality result. It is therefore consistent with a served-version change, but does not prove that it caused ABIS’s 27 October possible-version-change signal or that capability declined.

Do not merge that API alias with the separate AI Stupid Level watch for Gemini 3.5 Flash Lite. The labels are different. The monitor describes a reasoning score below its baseline for Flash Lite; Google’s page describes routing for the 3.5 Flash API name.

Tracker snapshot: zero confirmed alarms, two early warnings

AI Stupid Level’s tracker reports a 31 October 07:47 UTC snapshot: no open alarm among 25 models, with 66 of 75 per-suite detectors armed and three models still calibrating. Two models are on watch, not confirmed by a detector: DeepSeek V4.1 Flash is below baseline on coding and tool use; Gemini 3.5 Flash Lite is below baseline on reasoning. The operator says its fixed tasks run through each provider’s API and that detector confirmation requires sustained evidence. Its private suite and operator-controlled route limit the result to that monitor; it does not settle what happens in a reader’s consumer app or private workflow.

Older monitors do not fill the gap

BridgeBench’s NerfBench board still lists 16 October as the latest session for its four tracked series: GPT-6 Astra at 97.1%, GPT-6.1 Sol at 98.0%, Claude Sonnet 5.5 at 98.9%, and Claude Opus 5.5 at 105.8% relative to each model’s first tracked session. All are within its stated 90–110% band. That is not a fresh October 31 result.

The published method describes 50 private tasks, three attempts per task, and a frozen first tracked session as 100%. Its “power” score gives correctness 60%, output tokens 20%, and cost 20%; Codex is scored 75% correctness and 25% tokens because its cost is unavailable. A cheaper run can score higher even if correctness falls, and a more expensive or token-heavy run can score lower without the same size quality loss. The method says two complete, comparable sessions must fall outside the band on the same side before a change is confirmed. It does not publish per-session component scores in the board reviewed here. The reference is when tracking starts, not necessarily model launch day; baseline uncertainty is not shown on the public results page.

LiveNerf’s latest completed 10-day Opus 5.5 window remains labeled “no change”: −0.015 ± 0.018 across 78 calibrated items. The repository’s 29 October status said its later window was incomplete at 6 of 10 days. This is one pinned Claude Code subscription path, not a verdict about every Claude surface.

What readers report

A new r/ChatGPTcomplaints post describes instruction-following and image-generation problems and an intention not to renew Pro. The account is self-selected; the post has no paired prompts or image artifacts, model receipt, or denominator. It is a useful lead for a text-and-image replay, not proof of a model regression or churn rate.

What to do before you switch

1. If an API task uses gemini-3.5-flash, save the requested model string and available response metadata. Compare a safe repeated task against the currently documented gemini-3.6-flash path with prompt, settings, and input held fixed.
2. If the request fails or never returns, check the named API component and status history before scoring model quality.
3. If an answer completes but is worse, compare correctness, correction time, output size, cost, and tool behavior separately. Keep private prompts and images local.
4. Treat an early tracker watch as a reason to test the specific capability, not as a reason to switch every task or every model in the family.

Evidence checked 31 October 2026. Provider documentation establishes what Google currently documents, not the exact date of a route change. Monitor snapshots are operator-published; community posts identify leads but not their prevalence.