Umans GLM 5.2 Retired
no longer available; use umans-glm-5.3
retired Sep 10, 2026 · replaced by umans-glm-5.3 · weights ↗
85.4tok/s
throughput · p50 · whole period
1.79s
TTFT · p50 · whole period
98.85%
uptime · whole period
GLM 5.2 is our best model for coding right now, with a 400K context window for large codebases. Vision is available on the Anthropic Messages API (`/v1/messages`) only, through a server-side handoff (GLM 5.2 generates the text, Kimi preprocesses the image); that handoff will be retired soon in favour of more efficient client-side image handling. Deprecated: use `umans-glm-5.3` instead (sunset 2026-09-10).
Trends
Speed over its final 90 days
Jun 14, 2026retired Sep 10, 2026Sep 12, 2026
Jun 14, 2026retired Sep 10, 2026Sep 12, 2026
Changelog
Events for Umans GLM 5.2
Sep 102026
Retired: Umans GLM 5.2 Retired
umans-glm-5.2 reached its sunset and was retired in favour of GLM 5.3: it leaves the catalog and the model pickers, and its history stays on the past-models list. Requests still pinned to the old id keep routing for a short grace tail - migrate to umans-glm-5.3 (same GLM lineage, 1M context) now; a final cutoff date will be announced ahead of the hard stop.
Older events 8
Jul 202026
Planned maintenance: Umans GLM 5.2 Maintenance
We're making a change to GLM 5.2 on 2026-07-20, from 11:15 to 12:00 CET. During the window, around 30 to 40 minutes, GLM 5.2 responses may noticeably be slower than usual. Requests still go through, and other models are unaffected.
The work is aimed at making GLM 5.2 start responding faster once it lands.
Jul 102026
Resolved: Umans GLM 5.2 Resolved
The incident is resolved. Throughout the outage, most requests continued to be served, and a subset of users were affected. Umans GLM 5.2 is still running at reduced capacity, so responses may be slower than usual at peak times. We will post an update once full capacity is restored.
Jul 102026
Major outage: Umans GLM 5.2 Incident
We are currently experiencing a major outage affecting Umans GLM 5.2. Other models are unaffected. Our team is fully mobilized and working to restore normal operation as quickly as possible. We will post updates here as the situation evolves.
Jul 92026
GLM 5.2 performance stabilized, still on reduced capacity Resolved
GLM 5.2 performance has stabilized after deploying the prefill kernel update and selective prioritization for interactive requests.
We’re still operating today in reduced-capacity mode while capacity is being restored, but the service is holding and requests are flowing normally. We’ll keep monitoring closely and update here if anything changes.
Jul 92026
Degraded performance on Umans GLM 5.2 Incident
We’re currently seeing degraded performance on Umans GLM 5.2, mainly higher time-to-first-token and uneven streaming speed.
Requests are still going through, but the experience can feel slower than usual.
We’re investigating and applying mitigations. We’ll update here once things are back to target.
Jul 62026
Resolved: back to full capacity Resolved
Hardware capacity was restored and both umans-glm-5.2 and umans-kimi-k2.7 are back to normal speed. During the outage the service ran in a reduced-capacity mode that favoured continuity over speed: requests kept flowing, at the cost of an uneven experience. The affected window is shaded on each model's speed trends.
Jul 22026
Incident: hardware outage, running at reduced capacity Incident
A hardware failure took part of our GPU fleet offline. We failed over to reduced capacity to keep the service available: umans-glm-5.2 and umans-kimi-k2.7 stayed up, but slower than usual and with an uneven experience under load. Live updates were posted on Discord throughout.
Jun 212026
Released to production: Umans GLM 5.2 Released
umans-glm-5.2 was released as the long-context model, with a 405K context window, after a pre-release period that started Jun 16.