LLM Model Deprecations & Retirement Dates
As of August 8, 2026 — 33 legacy, deprecated, and retired models tracked. Raw dataset: data.json.
Shutting down soon
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-08.