Fireworks AI Outage History

150 incidents recorded over the last 365 days, 150 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded Fireworks AI Incident

Fireworks AI incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 24, 2026Service Degradation for Kimi K2.6We've resolved the incident and the affected service is now operational.7 minResolved
Aug 24, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.4 minResolved
Aug 23, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.5 minResolved
Aug 23, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.27 minResolved
Aug 23, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.11 minResolved
Aug 23, 2026Service Degradation for Qwen 3.8 MaxWe've resolved the incident and the affected service is now operational.3 minResolved
Aug 23, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.4 minResolved
Aug 23, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.3 minResolved
Aug 22, 2026Service Degradation for Minimax M2.7We've resolved the incident and the affected service is now operational.4 minResolved
Aug 22, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.5 minResolved
Aug 22, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.5 minResolved
Aug 22, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.2 minResolved
Aug 22, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.53 minResolved
Aug 22, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.25 minResolved
Aug 22, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.6 minResolved
Aug 22, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.39 minResolved
Aug 21, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.3 minResolved
Aug 21, 2026Service Degradation for Kimi K3 USWe've resolved the incident and the affected service is now operational.9 minResolved
Aug 21, 2026Service Degradation for Kimi K3 USWe've resolved the incident and the affected service is now operational.14 minResolved
Aug 21, 2026Service Degradation for Kimi K3 USWe've resolved the incident and the affected service is now operational.5 minResolved
Aug 21, 2026Service Degradation for Kimi K3 USWe've resolved the incident and the affected service is now operational.4 minResolved
Aug 21, 2026Service Degradation for Kimi K3 USWe've resolved the incident and the affected service is now operational.38 minResolved
Aug 21, 2026Service Degradation for Kimi K3 USWe've resolved the incident and the affected service is now operational.42 minResolved
Aug 21, 2026Service Degradation for Kimi K3 USWe've resolved the incident and the affected service is now operational.11 minResolved
Aug 21, 2026Service Degradation for Kimi K3 USWe've resolved the incident and the affected service is now operational.2 minResolved
Aug 21, 2026Service Degradation for Kimi K3 USWe've resolved the incident and the affected service is now operational.14 minResolved
Aug 20, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.16 minResolved
Aug 20, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.14 minResolved
Aug 20, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.4 minResolved
Aug 20, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.7 minResolved
Aug 20, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.3 minResolved
Aug 20, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.1 minResolved
Aug 20, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.11 minResolved
Aug 19, 2026Service Degradation for Qwen 3.8 MaxWe've resolved the incident and the affected service is now operational.5 minResolved
Aug 19, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.1h 29mResolved
Aug 19, 2026Service Degradation for one of our Serverless modelsThe incident is resolved11h 7mResolved
Aug 19, 2026Service Degradation for Kimi K3We've resolved the incident and the affected service is now operational.21 minResolved
Aug 19, 2026Service Degradation for GLM 5.2 FastGLM 5.2 Fast performance has recovered and the service is operating normally. We have resolved this incident.-122 minResolved
Aug 18, 2026Service Degradation for GLM 5.2 FastWe've resolved the incident and the affected service is now operational.18 minResolved
Aug 18, 2026Service Degradation for Kimi K3We've resolved the incident and the affected service is now operational.6 minResolved
Aug 18, 2026Service Degradation for GLM 5.2 FastWe've resolved the incident and the affected service is now operational.1h 4mResolved
Aug 18, 2026Service Degradation for GLM 5.2 FastWe've resolved the incident and the affected service is now operational.4 minResolved
Aug 18, 2026Kimi K3 service disruptionKimi K3 availability has recovered and the service is operating normally. We have resolved this incident.1h 9mResolved
Aug 18, 2026Service Degradation for Kimi K3We've resolved the incident and the affected service is now operational.52 minResolved
Aug 18, 2026Service Degradation for GLM 5.2 FastWe've resolved the incident and the affected service is now operational.23 minResolved
Aug 17, 2026Service Degradation for Qwen 3.8 MaxWe've resolved the incident and the affected service is now operational.8 minResolved
Aug 17, 2026Service Degradation for Qwen 3.8 MaxWe've resolved the incident and the affected service is now operational.6 minResolved
Aug 17, 2026Service Degradation for Qwen 3.8 MaxWe've resolved the incident and the affected service is now operational.4 minResolved
Aug 16, 2026Service Degradation for Kimi K3 FastWe've resolved the incident and the affected service is now operational.10 minResolved
Aug 16, 2026Service Degradation for Kimi K3 FastWe've resolved the incident and the affected service is now operational.6 minResolved
Aug 16, 2026Service Degradation for Kimi K3 FastWe've resolved the incident and the affected service is now operational.16 minResolved
Aug 16, 2026Service Degradation for Kimi K2.7 Code, Kimi K2.7 Code FastWe've resolved the incident and the affected service is now operational.9 minResolved
Aug 15, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.6 minResolved
Aug 14, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.9 minResolved
Aug 14, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.9 minResolved
Aug 14, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.10 minResolved
Aug 14, 2026Service Degradation for GLM 5.2 FastWe've resolved the incident and the affected service is now operational.9 minResolved
Aug 14, 2026Service Degradation for Kimi K3 USWe've resolved the incident and the affected service is now operational.10 minResolved
Aug 14, 2026Service Degradation for Kimi K3 USWe've resolved the incident and the affected service is now operational.15 minResolved
Aug 14, 2026Service Degradation for Kimi K3 USWe've resolved the incident and the affected service is now operational.9 minResolved
Aug 14, 2026Service Degradation for Kimi K3 USWe've resolved the incident and the affected service is now operational.5 minResolved
Aug 14, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.3 minResolved
Aug 14, 2026Service Degradation for Kimi K3We've resolved the incident and the affected service is now operational.23 minResolved
Aug 14, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.18 minResolved
Aug 14, 2026Service Degradation for Kimi K3We've resolved the incident and the affected service is now operational.4 minResolved
Aug 14, 2026Service Degradation for Kimi K3We've resolved the incident and the affected service is now operational.26 minResolved
Aug 14, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.18 minResolved
Aug 14, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.11 minResolved
Aug 13, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.16 minResolved
Aug 13, 2026Service Degradation for Kimi K3We've resolved the incident and the affected service is now operational.5h 47mResolved
Aug 13, 2026Service Degradation for DeepSeek V4 ProWe've resolved the incident and the affected service is now operational.15 minResolved
Aug 12, 2026Service Degradation for Kimi K3 FastRoot issue has been resolved, service is healthy.3h 19mResolved
Aug 12, 2026Service Degradation for Kimi K3 FastWe've resolved the incident and the affected service is now operational.1h 42mResolved
Aug 12, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.9 minResolved
Aug 12, 2026Service Degradation for Kimi K2.7 Code, Kimi K2.7 Code FastWe've resolved the incident and the affected service is now operational.6 minResolved
Aug 12, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.20 minResolved
Aug 12, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.30 minResolved
Aug 12, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.40 minResolved
Aug 11, 2026Service Degradation for Kimi K2.6We've resolved the incident and the affected service is now operational.7 minResolved
Aug 11, 2026Service Degradation for Kimi K2.6 FastWe've resolved the incident and the affected service is now operational.34 minResolved
Aug 11, 2026Service Degradation for Kimi K2.7 Code, Kimi K2.7 Code FastWe've resolved the incident and the affected service is now operational.33 minResolved
Aug 11, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.44 minResolved
Aug 11, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.1h 9mResolved
Aug 11, 2026Service Degradation for GLM 5.2We've resolved the incident and the affected service is now operational.1h 3mResolved
Aug 11, 2026Service Degradation for Minimax M3We've resolved the incident and the affected service is now operational.1h 58mResolved
Aug 11, 2026Service Degradation for Kimi K3 FastWe've resolved the incident and the affected service is now operational.1h 32mResolved
Aug 11, 2026Service Degradation for Kimi K2.6 FastWe've resolved the incident and the affected service is now operational.1h 42mResolved
Aug 11, 2026Cloud Service Provider OutageAll services are now operational.46h 35mResolved
Aug 10, 2026Service Degradation for Kimi K3 US, Kimi K3 US We've resolved the incident and the affected service is now operational.22 minResolved
Aug 10, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.4 minResolved
Aug 10, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.8 minResolved
Aug 10, 2026Service Degradation for Kimi K2.6We've resolved the incident and the affected service is now operational.41 minResolved
Aug 10, 2026Service Degradation for Kimi K2.6We've resolved the incident and the affected service is now operational.11 minResolved
Aug 10, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.10 minResolved
Aug 10, 2026Service Degradation for Kimi K2.7 Code, Kimi K2.7 Code FastWe've resolved the incident and the affected service is now operational.6 minResolved
Aug 10, 2026Service Degradation for Kimi K2.7 Code, Kimi K2.7 Code FastWe've resolved the incident and the affected service is now operational.8 minResolved
Aug 8, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.21 minResolved
Aug 7, 2026Service Degradation for Kimi K2.6We've resolved the incident and the affected service is now operational.6 minResolved
Aug 7, 2026Service Degradation for one of our Serverless modelsWe've resolved the incident and the affected service is now operational.10 minResolved
Aug 7, 2026Reduced cache hit rates for Kimi K3 The issue has been resolved.6h 23mResolved
Aug 7, 2026Service Degradation for GLM 5.2 FastWe've resolved the incident and the affected service is now operational.3h 40mResolved
Aug 7, 2026Service Degradation for Kimi K3 US, Kimi K3 US We've resolved the incident and the affected service is now operational.43 minResolved
Aug 7, 2026Service Degradation for Kimi K3 US, Kimi K3 US We've resolved the incident and the affected service is now operational.7 minResolved
Aug 7, 2026Service Degradation for Kimi K3We've resolved the incident and the affected service is now operational.5 minResolved
Aug 6, 2026Service Degradation for Minimax M3The issue has now been resolved.12 minResolved
Aug 6, 2026Service Degradation for Minimax M3We've resolved the incident and the affected service is now operational.30 minResolved
Aug 5, 2026Service Degradation for one of our models on ServerlessWe've resolved the incident and the affected service is now operational.30 minResolved
Aug 5, 2026Service Degradation for one of our models on ServerlessWe've resolved the incident and the affected service is now operational.4 minResolved
Aug 5, 2026Service Degradation for one of our models on ServerlessWe've resolved the incident and the affected service is now operational.22 minResolved
Aug 5, 2026Service Degradation for one of our models on ServerlessWe've resolved the incident and the affected service is now operational.15 minResolved
Aug 5, 2026Service Degradation for one of our models on ServerlessWe've resolved the incident and the affected service is now operational.6 minResolved
Aug 4, 2026Service Degradation for one of our models on ServerlessWe've resolved the incident and the affected service is now operational.3h 5mResolved
Aug 4, 2026Service Degradation for one of our models on ServerlessWe've resolved the incident and the affected service is now operational.4 minResolved
Aug 4, 2026Service Degradation for one of our models on ServerlessWe've resolved the incident and the affected service is now operational.20 minResolved
Aug 3, 2026Service Degradation for one of our models on ServerlessWe've resolved the incident and the affected service is now operational.4 minResolved
Aug 3, 2026Service Degradation for one of our models on ServerlessWe've resolved the incident and the affected service is now operational.4 minResolved
Aug 3, 2026Service Degradation for one of our models on ServerlessWe've resolved the incident and the affected service is now operational.6h 52mResolved
Aug 3, 2026Service Degradation for one of our models on ServerlessWe've resolved the incident and the affected service is now operational.18 minResolved
Aug 3, 2026Service Degradation for one of our models on ServerlessWe've resolved the incident and the affected service is now operational.18 minResolved
Aug 2, 2026Service Degradation for one of our models on ServerlessWe've resolved the incident and the affected service is now operational.3 minResolved
Aug 2, 2026Service Degradation for one of our models on ServerlessWe've resolved the incident and the affected service is now operational.40 minResolved
Aug 2, 2026Service Degradation for one of our models on ServerlessWe've resolved the incident and the affected service is now operational.7 minResolved
Aug 1, 2026Service Degradation for Qwen 3.7 PlusWe've resolved the incident and the affected service is now operational.3h 49mResolved
Jul 31, 2026Service Degradation for one of our models on ServerlessWe've resolved the incident and the affected service is now operational.37 minResolved
Jul 31, 2026Service Degradation for one of our models on ServerlessWe've resolved the incident and the affected service is now operational.43 minResolved
Jul 31, 2026Service Degradation for one of our models on ServerlessWe've resolved the incident and the affected service is now operational.32 minResolved
Jul 30, 2026Service Degradation for One of our models on ServerlessWe've resolved the incident and the affected service is now operational.13 minResolved
Jul 30, 2026Service Degradation for  We've resolved the incident and the affected service is now operational.19 minResolved
Jul 30, 2026Service Degradation for  We've resolved the incident and the affected service is now operational.15 minResolved
Jul 30, 2026Service Degradation for  We've resolved the incident and the affected service is now operational.13 minResolved
Jul 30, 2026Service Degradation for  We've resolved the incident and the affected service is now operational.18 minResolved
Jul 30, 2026Service Degradation for Serverless → Kimi K3 US We've resolved the incident and the affected service is now operational.5 minResolved
Jul 30, 2026Service Degradation for Serverless → Kimi K3 US We've resolved the incident and the affected service is now operational.15 minResolved
Jul 30, 2026Service Degradation for Serverless → Kimi K3 US We've resolved the incident and the affected service is now operational.16 minResolved
Jul 27, 2026Service Degradation for Serverless → Kimi K2.6 We've resolved the incident and the affected service is now operational.3 minResolved
Jul 27, 2026Service Degradation for Serverless → GLM 5.2 Fast We've resolved the incident and the affected service is now operational.6 minResolved
Jul 27, 2026Service Degradation for Serverless → Kimi K2.6 We've resolved the incident and the affected service is now operational.11 minResolved
Jul 27, 2026Service Degradation for  We've resolved the incident and the affected service is now operational.3 minResolved
Jul 24, 2026Service Degradation for  We've resolved the incident and the affected service is now operational.9 minResolved
Jul 24, 2026Service Degradation for Serverless → GLM 5.2 Fast We've resolved the incident and the affected service is now operational.11h 32mResolved
Jul 24, 2026Service Degradation for Serverless → Minimax M3 We've resolved the incident and the affected service is now operational.5 minResolved
Jul 22, 2026Service Degradation for Serverless → MiniMax 2.7 We've resolved the incident and the affected service is now operational.5 minResolved
Jul 22, 2026Service Degradation for Serverless → Kimi K2.6 We've resolved the incident and the affected service is now operational.15 minResolved
Jul 20, 2026Service Degradation for Kimi K2.6 We've resolved the incident and the affected service is now operational.24 minResolved
Jul 20, 2026Service Degradation for Kimi K2.7 Code, Kimi K2.7 Code Fast We've resolved the incident and the affected service is now operational.8 minResolved
Jul 19, 2026Service Degradation for Minimax M3 We've resolved the incident and the affected service is now operational.11 minResolved
Jul 17, 2026Service Degradation for Minimax M3 We've resolved the incident and the affected service is now operational.7 minResolved
Jun 22, 2026Service Degradation for DeepSeek V4 FlashWe've resolved the incident and the affected service is now operational.59 minResolved
Jun 19, 2026Service Degradation for  We've resolved the incident and the affected service is now operational.1h 24mResolved
Jun 12, 2026Service Degradation for DeepSeek V4 Flash We've resolved the incident and the affected service is now operational.13 minResolved

How to Read This Fireworks AI Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Fireworks AI acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Fireworks AI outage in this window ran 1d 22h, against a mean recovery of 59 min. If you depend on Fireworks AI in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.