Google has notified Vertex/Agent Platform customers that the Gemini 2.5 series — Pro, Flash, and Flash-Lite — will be retired no earlier than mid-October 2026, after extending the date once from June under community pressure; AI Studio runs a separate schedule. Google's own lifecycle table names Flash-tier models (Gemini 3.5 Flash / Flash-Lite) as the designated replacements — including for 2.5 Pro — and no generally available Pro-class successor appears in the supplied sources: the Pro-line successors that surface (Gemini 3.1 Pro per GitHub's deprecation notice, a reportedly preview-bound Gemini 4 Pro per Reddit) are all previews. Third-party migration writeups report a real long-context regression (128k MRCR) in Flash replacements on document-QA workloads and advise side-by-side evals at 100k+ tokens — independent support for the claim that this migration degrades long-document reasoning. Caveats: retirement dates differ across sources (Oct 16 vs Oct 20 in the official table), successor naming is inconsistent (Gemini 3 / 3.1 / 3.5 / 4), and a Google forum reply reportedly grandfathers existing active users indefinitely.
A dated, corroborated instance of exactly what Model Perishability and Vendor Lock-In already hold — Google retiring the workhorse model with no GA Pro-class successor and steering users to a down-tier with reported long-context regression — so nothing new for his canon; but it lands on his own stack: dev:technology.gemini is the primary creative model in his LiteLLM router and Portfolio/podcast pin Gemini, making 'which model IDs do my projects reference, and does the AI Studio schedule follow the Agent Platform one?' a concrete check rather than a hypothetical. The third-party 128k MRCR regression finding also independently corroborates his evals-before-model-swap discipline.
ip:concept.model-perishabilityip:concept.vendor-lock-inip:concept.perishable-prompt-layerdev:technology.geminidev:project.portfoliodev:project.podcastradar:person.geminiradar:concept.model-lifecycleradar:concept.model-migrationradar:openai-gpt55-retirementradar:deepseek-v4-pro-soft-retirementradar:gemini-37-flash-model-selection
queries asked of Scott's wikis
- model perishability hosted-model deprecation doctrine
- pinned model identifiers breaking production integrations
- long-context retrieval regression RAG evals before model swap
- model abstraction layer fallback routing hosted APIs
- local open-weight models as hedge against API deprecation
- Gemini API integration model dependency
now 0 pts/hpeak 90 pts/hcomments 0/hpeers p14momentum: steady2 platformsage 709h
points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion
2026-09-30T08:57:43Z
The Gemini Pro 4 leak completed its run as the case's dominant periphery event — 506/283 at a ~104 pts/h peak, now stalled to zero — while its community-rejected reception held, so the case's meaning is unchanged: a corroborated schedule-plus-gap risk whose open questions (leak authenticity, grandfathering scope, another postponement) can only resolve at official checkpoints before Oct 16-20. Heat stays medium rather than the loud-spread reading the magnitude valve flags because the spread was rumor froth that has already cooled, but the shrinking runway to a hard deadline and Scott's pinned Gemini stack keep it above low — regular attention, not an hours-level ping.
2026-09-28T08:26:49Z
First named candidate for the missing GA Pro-class successor surfaced — a 'Gemini Pro 4' leak — but its community-rejected reception (0.75 ratio, dismissive top comments, 'treat as a rumor' in the post itself) keeps it below the credibility bar, so the case's meaning is unchanged: a corroborated schedule-plus-gap risk awaiting leak verification or an official GA/preview before the mid-October retirement. Heat rises to medium because the leak post is a 90th-percentile mover inside a shrinking runway to a hard deadline — an attention call, not a belief change.
2026-09-28T08:23:14Z
evidence attached: reddit.post.1ws8erf — Widely circulating (43/43 comments) Gemini Pro 4 leak, if real, is the missing GA pro-class replacement the October-retirement case hinges on — unverified, but directly bears on that hypothesis.
2026-09-25T19:08:07Z
Nothing here changes the case's meaning: the velocity spike was a transient blip on an idle thread (+1 point, one speculative postponement comment), with the current rate at 0 pts/h and 31st percentile. Still a corroborated schedule-plus-gap risk holding for its natural checkpoints — a successor reaching GA or early-October migration guidance — not for comment churn.
2026-09-24T04:52:34Z
grounded: known/medium — A dated, corroborated instance of exactly what Model Perishability and Vendor Lock-In already hold — Google retiring the workhorse model with no GA Pro-class su
2026-09-24T04:46:44Z
The gap half of the claim now has independent support — Gemini 4 Pro reported nearing preview-only release while Google forum guidance steers new projects to Flash-tier — moving the case beyond one user's account to a corroborated schedule-plus-gap risk, softened by reports that existing users are grandfathered.
2026-09-24T04:28:12Z
evidence attached: reddit.post.1wor7lh — Gemini 4 Pro nearing preview (not GA) is direct timing evidence for whether a Pro-class replacement lands before the October 2.5 retirement.
2026-09-12T03:25:35Z
grounded: known/medium — Scott already argues for replaceable, re-evaluated model dependencies in Model Perishability; the supplied radar hits track analogous retirements, not this Gemi
2026-09-12T03:21:55Z
case created — A dated model-retirement claim creates a bounded migration-risk episode, but the schedule and replacement capability gap currently rest on one user's uncorroborated account.