ONE MODEL, EVERY PLATFORM

`deepseek-v3.2` deprecation and shutdown dates on every platform

deepseek-v3.2 is tracked on 5 providers and hosting routes. First to go: Azure (Microsoft Azure / Foundry) shuts down DeepSeek-V3.2@1 on Nov 1, 2027.

Last updated Oct 23, 2026

AzureMicrosoft Azure / Foundry

deepseek-v3.2 on Azure
Date	Model	Status	Replacement	Source
Nov 1, 2027	`DeepSeek-V3.2@1`	Shuts down374 days	`DeepSeek-V4.1-Flash`	Notice ↗

VertexGoogle Cloud Vertex AI

deepseek-v3.2 on Vertex
Date	Model	Status	Replacement	Source
Oct 21, 2026	`deepseek-v3.2-maas`	Shut down	Alternative: `Self-deploy DeepSeek-V3.2 on Model Garden`	Notice ↗

NovitaAI

deepseek-v3.2 on NovitaAI
Date	Model	Status	Replacement	Source
Sep 29, 2026	`deepseek/deepseek-v3.2`	Shut down	`deepseek/deepseek-v4.1-flash`	Notice ↗

Nebius

deepseek-v3.2 on Nebius
Date	Model	Status	Replacement	Source
Jun 22, 2026	`deepseek-ai/DeepSeek-V3.2`	Shut down	None published	Notice ↗

Friendli

deepseek-v3.2 on Friendli
Date	Model	Status	Replacement	Source
—	`deepseek-ai/DeepSeek-V3.2`	No deprecation notice tracked	None published	Notice ↗

Every provider sets its own dates

A deadline on one platform says nothing about another: OpenAI, Azure, Amazon Bedrock, Google Vertex AI and model routers each retire their own copies on their own schedule. Snapshots of the same model (for example dated versions) are listed separately because each has its own date. Rows marked “No deprecation notice tracked” mean ModelClock has not seen a retirement notice for that route, not that one cannot exist.