ONE MODEL, EVERY PLATFORM

`glm-5` deprecation and shutdown dates on every platform

glm-5 is tracked on 6 providers and hosting routes. No upcoming shutdown date is published. Most recently, Vertex (Google Cloud Vertex AI) shut down glm-5-maas on Oct 21, 2026.

Last updated Oct 23, 2026

VertexGoogle Cloud Vertex AI

glm-5 on Vertex
Date	Model	Status	Replacement	Source
Oct 21, 2026	`glm-5-maas`	Shut down	Alternative: `Self-deploy GLM 5 on Model Garden`	Notice ↗

Together AI

glm-5 on Together AI
Date	Model	Status	Replacement	Source
Jul 29, 2026	`zai-org/GLM-5`	Shut down	`zai-org/GLM-5.1`	Notice ↗

Nebius

glm-5 on Nebius
Date	Model	Status	Replacement	Source
Jun 22, 2026	`zai-org/GLM-5`	Shut down	None published	Notice ↗

IteraCompute

glm-5 on IteraCompute
Date	Model	Status	Replacement	Source
—	`GLM-5`	No deprecation notice tracked	None published	Notice ↗

Z.ai

glm-5 on Z.ai
Date	Model	Status	Replacement	Source
—	`GLM-5`	No deprecation notice tracked	None published	Notice ↗

Friendli

glm-5 on Friendli
Date	Model	Status	Replacement	Source
—	`zai-org/GLM-5`	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.