Incident history
Oct 31, 2026
23:44–23:58 · 14 min
We've resolved the incident and the affected service is now operational.
Oct 31, 2026 · 23:43 → 23:5618:22–18:28 · 6 min
We've resolved the incident and the affected service is now operational.
Oct 31, 2026 · 18:21 → 18:26Oct 30, 2026
We are experiencing service degradation impacting deployment creation, dedicated training, and batch inference services. We are working to resolve these issues and will provide updates here.
Oct 30, 2026 · 20:5119:38–20:14 · 36 min
We've resolved the incident and the affected service is now operational.
Oct 30, 2026 · 19:37 → 20:1310:28–11:00 · 32 min
We've resolved the incident and the affected service is now operational.
Oct 30, 2026 · 10:28 → 11:00Oct 28, 2026
15:08–15:16 · 8 min
We've resolved the incident and the affected service is now operational.
Oct 28, 2026 · 15:08 → 15:1607:14–08:10 · 56 min
We've resolved the incident and the affected service is now operational.
Oct 28, 2026 · 07:13 → 08:10We've resolved the incident and the affected service is now operational.
Oct 28, 2026 · 05:56 → 05:5805:46–05:50 · 4 min
We've resolved the incident and the affected service is now operational.
Oct 28, 2026 · 05:45 → 05:4805:36–05:40 · 4 min
We've resolved the incident and the affected service is now operational.
Oct 28, 2026 · 05:35 → 05:39Oct 27, 2026
12:26–12:50 · 24 min
We've resolved the incident and the affected service is now operational.
Oct 27, 2026 · 12:26 → 12:5001:08–01:38 · 29 min
We've resolved the incident and the affected service is now operational.
Oct 27, 2026 · 01:07 → 01:37Oct 26, 2026
23:50–23:56 · 6 min
We've resolved the incident and the affected service is now operational.
Oct 26, 2026 · 23:49 → 23:5623:04–23:26 · 22 min
We've resolved the incident and the affected service is now operational.
Oct 26, 2026 · 23:03 → 23:2619:48–22:22 · 2h 34m
We've resolved the incident and the affected service is now operational.
Oct 26, 2026 · 19:47 → 22:21We've resolved the incident and the affected service is now operational.
Oct 26, 2026 · 19:43 → 19:4418:40–18:48 · 8 min
We've resolved the incident and the affected service is now operational.
Oct 26, 2026 · 18:40 → 18:4718:00–18:14 · 14 min
We've resolved the incident and the affected service is now operational.
Oct 26, 2026 · 17:59 → 18:13Oct 25, 2026
We've resolved the incident and the affected service is now operational.
Oct 25, 2026 · 23:29 → 23:33Oct 23, 2026
15:42–16:38 · 56 min
15:23–15:36 · 14 min
13:59–15:19 · 1h 19m
13:34–13:52 · 18 min
We've resolved the incident and the affected service is now operational.
Oct 23, 2026 · 13:33 → 16:38Oct 22, 2026
We've resolved the incident and the affected service is now operational.
Oct 22, 2026 · 22:05 → 22:06We've resolved the incident and the affected service is now operational.
Oct 22, 2026 · 20:52 → 20:53We've resolved the incident and the affected service is now operational.
Oct 22, 2026 · 17:26 → 17:5017:00–18:00 · 1h
We've resolved the incident and the affected service is now operational.
Oct 22, 2026 · 02:04 → 02:05We've resolved the incident and the affected service is now operational.
Oct 22, 2026 · 00:34 → 01:30We've resolved the incident and the affected service is now operational.
Oct 22, 2026 · 00:13 → 00:1400:00–02:00 · 2h
Oct 21, 2026
09:00–10:00 · 1h
We've resolved the incident and the affected service is now operational.
Oct 21, 2026 · 08:56 → 09:58We've resolved the incident and the affected service is now operational.
Oct 21, 2026 · 05:28 → 05:5805:00–06:00 · 1h
We've resolved the incident and the affected service is now operational.
Oct 21, 2026 · 01:14 → 01:20Oct 20, 2026
We've resolved the incident and the affected service is now operational.
Oct 20, 2026 · 19:25 → 19:36We've resolved the incident and the affected service is now operational.
Oct 20, 2026 · 19:23 → 19:56We've resolved the incident and the affected service is now operational.
Oct 20, 2026 · 18:19 → 18:4718:00–20:00 · 2h
The elevated response latency affecting some serverless models has been resolved. Response latency has returned to normal.
Oct 20, 2026 · 01:29 → 02:50Oct 19, 2026
We've resolved the incident and the affected service is now operational.
Oct 19, 2026 · 23:05 → 23:2323:00–00:00 · 1h
We are seeing impacted performance for GLM 5.3. We are actively investigating.
Oct 19, 2026 · 20:11We've resolved the incident and the affected service is now operational.
Oct 19, 2026 · 18:29 → 21:1018:00–21:00 · 3h
We've resolved the incident and the affected service is now operational.
Oct 19, 2026 · 01:08 → 01:2601:00–02:00 · 1h
Oct 18, 2026
07:00–08:00 · 1h
We've resolved the incident and the affected service is now operational.
Oct 18, 2026 · 06:59 → 07:21We've resolved the incident and the affected service is now operational.
Oct 18, 2026 · 03:16 → 03:3303:00–04:00 · 1h
Oct 17, 2026
We've resolved the incident and the affected service is now operational.
Oct 17, 2026 · 08:22 → 08:55We've resolved the incident and the affected service is now operational.
Oct 17, 2026 · 07:22 → 07:3707:00–09:00 · 2h
Oct 15, 2026
We've resolved the incident and the affected service is now operational.
Oct 15, 2026 · 08:48 → 09:05We've resolved the incident and the affected service is now operational.
Oct 15, 2026 · 08:09 → 09:2507:00–10:00 · 3h
We've resolved the incident and the affected service is now operational.
Oct 15, 2026 · 06:45 → 08:05Oct 14, 2026
Service has been restored for all affected serverless models. This incident is resolved.
Oct 14, 2026 · 23:06 → 01:5323:00–01:00 · 2h
We've resolved the incident and the affected service is now operational.
Oct 14, 2026 · 22:33 → 22:46We've resolved the incident and the affected service is now operational.
Oct 14, 2026 · 21:24 → 21:26We've resolved the incident and the affected service is now operational.
Oct 14, 2026 · 01:26 → 01:29Oct 13, 2026
We've resolved the incident and the affected service is now operational.
Oct 13, 2026 · 09:37 → 09:40We've resolved the incident and the affected service is now operational.
Oct 13, 2026 · 05:09 → 07:5405:00–08:00 · 3h
Oct 12, 2026
13:00–18:00 · 5h
We've resolved the incident and the affected service is now operational.
Oct 12, 2026 · 12:48 → 18:06We've resolved the incident and the affected service is now operational.
Oct 12, 2026 · 12:33 → 12:33We've resolved the incident and the affected service is now operational.
Oct 12, 2026 · 11:39 → 11:4010:00–11:00 · 1h
We've resolved the incident and the affected service is now operational.
Oct 12, 2026 · 09:59 → 10:22We've resolved the incident and the affected service is now operational.
Oct 12, 2026 · 01:00 → 01:08Oct 11, 2026
We've resolved the incident and the affected service is now operational.
Oct 11, 2026 · 13:34 → 14:0413:00–14:00 · 1h
Oct 10, 2026
We are seeing impacted performance for Kimi K3 Fast. We are actively investigating.
Oct 10, 2026 · 13:20We've resolved the incident and the affected service is now operational.
Oct 10, 2026 · 11:00 → 12:4511:00–18:00 · 7h
We've resolved the incident and the affected service is now operational.
Oct 10, 2026 · 10:06 → 10:08Oct 8, 2026
21:00–23:00 · 2h
The performance issue affecting GLM 5.3 Flash has been resolved.
Oct 8, 2026 · 20:49 → 22:36We've resolved the incident and the affected service is now operational.
Oct 8, 2026 · 19:17 → 19:30Oct 7, 2026
We've resolved the incident and the affected service is now operational.
Oct 7, 2026 · 21:29 → 21:40We've resolved the incident and the affected service is now operational.
Oct 7, 2026 · 19:02 → 19:13Oct 6, 2026
We've resolved the incident and the affected service is now operational.
Oct 6, 2026 · 15:26 → 15:26Oct 5, 2026
We've resolved the incident and the affected service is now operational.
Oct 5, 2026 · 18:51 → 19:15We've resolved the incident and the affected service is now operational.
Oct 5, 2026 · 17:15 → 17:41We've resolved the incident and the affected service is now operational.
Oct 5, 2026 · 14:32 → 14:33We've resolved the incident and the affected service is now operational.
Oct 5, 2026 · 06:21 → 06:24Oct 4, 2026
We've resolved the incident and the affected service is now operational.
Oct 4, 2026 · 16:29 → 16:29Oct 2, 2026
We've resolved the incident and the affected service is now operational.
Oct 2, 2026 · 22:35 → 22:49Oct 1, 2026
We've resolved the incident and the affected service is now operational.
Oct 1, 2026 · 05:57 → 06:04