Every model leaves. Here is when.
Models step down in stages. First the apps, then the API, sometimes lingering on a cloud before they are gone for good. This page keeps the dates, and your agent can read them too.
One step for each date
3 Dec: DeepSeek-V4-Flash-0731 on Azure Foundry
Pick a provider, or a place.
The same model can leave on different dates in different places, so each place gets its own row. Gone means it has already left that place.
Leaving
- DeepSeek-V4-Flash-0731 leaves 3 Dec Azure Foundry · still available in 48 days Per Microsoft's Azure Foundry retirement schedule (read 15 Oct); an independent tracker agrees. · Provider's page
- DeepSeek-R1 leaves 30 Mar 2027 Amazon Bedrock · legacy in 6 months After that, requests fail · Per Amazon's Bedrock model lifecycle page (read 15 Oct). · Provider's page
- DeepSeek-V3.1 leaves 30 Mar 2027 Amazon Bedrock · legacy in 6 months After that, requests fail · Per Amazon's Bedrock model lifecycle page (read 15 Oct). · Provider's page
- DeepSeek-V3.1 leaves 30 Mar 2027 Amazon Bedrock · legacy in 6 months After that, requests fail · Per Amazon's Bedrock model lifecycle page (read 15 Oct). · Provider's page
- DeepSeek-V4-Flash leaves 20 Feb 2028 Azure Foundry · still available in 16 months Replacement: DeepSeek-V4-Flash-0731 · Per Microsoft's Azure Foundry retirement schedule (read 15 Oct); an independent tracker agrees. · Provider's page
- DeepSeek-V4-Pro leaves 20 Feb 2028 Azure Foundry · still available in 16 months Per Microsoft's Azure Foundry retirement schedule (read 15 Oct); an independent tracker agrees. · Provider's page
Already gone
- DeepSeek-R1 left 13 Aug Azure Foundry · retired 2 months ago Replacement: DeepSeek-V4-Pro · Per Microsoft's Azure Foundry retirement schedule (read 15 Oct); an independent tracker agrees. · Provider's page
- DeepSeek-R1-0528 left 13 Jul Azure Foundry · retired 3 months ago Replacement: DeepSeek-V4-Pro · Per Microsoft's Azure Foundry retirement schedule (read 15 Oct); an independent tracker agrees. · Provider's page
- DeepSeek-V3-0324 left 13 Jul Azure Foundry · retired 3 months ago Replacement: DeepSeek-V4-Flash · Per Microsoft's Azure Foundry retirement schedule (read 15 Oct); an independent tracker agrees. · Provider's page
- DeepSeek-V3.1 left 13 Jul Azure Foundry · retired 3 months ago Replacement: DeepSeek-V4-Flash · Per Microsoft's Azure Foundry retirement schedule (read 15 Oct); an independent tracker agrees. · Provider's page
Your agent doesn't read this page. It asks.
With Aware connected, your agent calls aware_models. Name a model any way you like and it answers for every app, API and cloud. Name nothing and it gets whatever is changing in the next 90 days for the models you follow.
aware_models { "model": "gemini-robotics-er-1.6-preview", "surface": "gemini_api" }
gemini-robotics-er-1.6-preview on the Gemini API: Deprecated; the retirement date 31 Aug has passed and the source still lists it this way. Replacement: gemini-robotics-er-2-preview. Requests now fail.
Or paste this to your agent in any chat:
Use aware_models to check when the model you run on leaves each app, API and cloud. Tell me the dates that matter.
Not connected yet? Add the connector first.
Read from the source. Compared with a second.
Every day, Aware reads the providers' own deprecation pages: Anthropic, OpenAI, Google, AWS, Azure, Mistral and xAI. What a page says is shown as it is read, with the page it came from and the day it was read. Dates for the consumer apps are added by hand by the Aware team.
An independent tracker, deprecations.info, is compared with each row. Each one says whether the tracker agrees, and where they differ both dates are shown. If a provider moves a date, this page moves with it and says what it moved from. A person at Aware can check a date or set it by hand, and it says so when they have.