LLM Model Deprecations & Retirement Dates
As of September 7, 2026 — 35 legacy, deprecated, and retired models tracked. Raw dataset: data.json. Cite this: All AI Ask LLM Model Lifecycle Dataset, retrieved 2026-08-14.
Shutting down soon
No announced shutdowns in the next 90 days, as of September 7, 2026.
Full lifecycle table
Sorted by urgency: deprecated (soonest shutdown first), then legacy, then retired. 6 models have a dedicated migration guide, linked from their pricing page.
Recently retired
Methodology
- Every dated row links a provider source — a deprecation notice, models page, or changelog. We do not publish a date we can't source.
- A
—in the "Shuts down" column means no announced end date, not "no risk" — a legacy model can still be retired with little notice. - Each row carries its own verification date; rows are re-checked at least every 120 days, and our build fails if one goes stale.
- Price change is the successor's blended $/M tokens (3:1 input:output) versus this model's, from our live pricing registry.
- Related coverage: our post-mortem on the Grok 4.1 Fast deprecation.
Switching models is a one-line change
One gateway, one API key — run your old prompt against the retiring model and its successor side by side before you switch.
Try It FreeFAQ
How much notice do providers give before retiring a model?
It varies by provider and is often measured in weeks, not months. Groq gave roughly two months' notice for the Llama 3.x decommissions tracked here. Some providers give no advance notice at all — that is exactly the "legacy, no announced end date" state most rows on this page are in.
What happens to my API calls after a model shuts down?
The provider starts rejecting requests for that model id, usually with a 4xx error. If you are calling All AI Ask directly by model id, that call starts failing on the shutdown date — there is no automatic fallback.
Which models have no announced end date?
Every row below marked "Legacy" with no "Shuts down" date. A legacy model can still be actively served indefinitely — "superseded" and "scheduled for shutdown" are different things, and we don't collapse them into one.
Does All AI Ask switch models automatically when one is retired?
No. We route to whatever model id you specify, including retired ones (until the provider itself rejects the call). Switching model ids is a change you make deliberately — this page and the linked migration guides exist to make that decision easier.
Where do these dates come from?
Every row links a provider source — an official deprecation notice, models page, or changelog. Where we could not find a provider-published date, we publish no date rather than guess one.
How often is this page re-verified?
Each row carries its own verification date. Rows older than 120 days fail our build, so this page cannot silently go stale. Newest verification: 2026-08-14.
Batch 49 · lifecycle decision and evidence contributions. Surface verification: 2026-08-14. These are route-local, server-rendered fixtures; unavailable values are not inferred.
Model-lifecycle evidence-state resolver
Frozen Batch 49 fixture board. Formula / decision rule: resolved state = exact provider + host + model/version/alias + authoritative lifecycle evidence Boundary: Lifecycle state never transfers across unresolved providers, hosts, aliases, or dates.
| Frozen fixture / field ID | Joined inputs and observation | Calculated result | State |
|---|---|---|---|
batch49-lifecycle-m1-r1current · legacy/no-date · announced deprecation/no shutdown | provider=joined; host=official; model=exact; source=notice/models; announced=joined/none; shutdown=none; observed=2026-08-14 Current and legacy states are distinct; no-date rows do not receive an invented deadline. | state=current or legacy/no-date according to evidence | RESOLVED — date semantics preserved. |
batch49-lifecycle-m1-r2scheduled shutdown · retired | provider=joined; host=official; model=exact; source=notice; shutdown=2026-09-30/2026-07-01; prior=deprecated/scheduled Announced shutdown transitions to scheduled; past verified shutdown transitions to retired. | allowed transition=prior + authoritative date evidence | RESOLVED — lifecycle transition allowed. |
batch49-lifecycle-m1-r3conflicting source · same-name alternate host | provider=ambiguous; host=official/alternate; model=same-name; source dates=conflict; alias=unresolved The same display name does not join the serving host or exact model identity. | resolved state=Unavailable; preserve conflict | FAIL CLOSED — identity conflict. |
Provenance: Batch 49 lifecycle module 1 first-party evidence and surface verification date 2026-08-14. All AI Ask lifecycle registry. Missing joins fail closed.
30/60/90-day portfolio exposure board
Frozen Batch 49 fixture board. Formula / decision rule: urgency = earlier(verified shutdown − required lead time, observed retirement) Boundary: A fallback is not qualified merely because it shares a display name.
| Frozen fixture / field ID | Joined inputs and observation | Calculated result | State |
|---|---|---|---|
batch49-lifecycle-m2-r1interactive API · batch pipeline | owner=platform; endpoint=official; model=model-a; share=62%; shutdown=2026-09-30; lead=21d; fallback=qualified Owner, exact endpoint/model, request share, shutdown evidence, and fallback join. | action deadline=2026-09-09; urgency=30-day board | URGENT — migrate before deadline. |
batch49-lifecycle-m2-r2embedded model ID · two-provider fallback | owner=app; endpoint=official; model=model-b; share=18%; shutdown=Unavailable; fallback=provider-b same-name; qualification=missing No verified shutdown date exists and fallback identity/capability is not joined. | days remaining=Unavailable; action=qualify fallback, not auto-switch | UNAVAILABLE — evidence/qualification gap. |
batch49-lifecycle-m2-r3alternate-host same model · already-retired dependency | owner=batch; host=alternate; model=model-c; share=20%; retirement=verified; fallback=none; lead=14d Alternate host has a separate lifecycle identity; the workload still depends on a retired model. | urgency=immediate; action=stop/repoint with owner approval | CRITICAL — retired dependency. |
Provenance: Batch 49 lifecycle module 2 first-party evidence and surface verification date 2026-08-14. All AI Ask lifecycle registry. Missing joins fail closed.
Lifecycle dataset completeness and actionability audit
Frozen Batch 49 fixture board. Formula / decision rule: actionable = identity + authoritative lifecycle evidence + owner all joined Boundary: A complete-looking row without date semantics or an accountable owner is not actionable.
| Frozen fixture / field ID | Joined inputs and observation | Calculated result | State |
|---|---|---|---|
batch49-lifecycle-m3-r1exact shutdown date · earliest-possible date | model=exact; provider/host=joined; shutdown=2026-09-30; earliest=Unavailable; source=reachable; owner=platform Exact shutdown evidence is usable; earliest-possible semantics remain unavailable. | actionability=Yes for exact deadline; earliest=Unavailable | ACTIONABLE WITH LIMIT. |
batch49-lifecycle-m3-r2no announced date · named successor · successor without guide | model=legacy; shutdown=none; successor=model-d; guide=missing; evidence age=2026-08-14; owner=product Successor signal exists, but it is not an automatic migration verdict without a guide and qualification. | actionability=Partial; migration guide coverage=0% | PARTIAL — owner action required. |
batch49-lifecycle-m3-r3stale source · conflicting notice | model=model-e; source age=211d; reachable=No; notices=conflict; owner=missing; date semantics=ambiguous Stale and conflicting evidence leaves identity, date, and owner joins open. | actionable=No; state=Unavailable until reconciled | FAIL CLOSED — refresh and reconcile. |
Provenance: Batch 49 lifecycle module 3 first-party evidence and surface verification date 2026-08-14. All AI Ask lifecycle registry. Missing joins fail closed.