- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 28of 100
Summary
Fireworks AI says it saw impacted performance for GLM 5.3 starting at 02:30 UTC on 2026-11-15. At 03:13 UTC the provider said the incident was resolved and the affected service was operational.
Written by anthropic/claude-haiku-5.5 from Fireworks AI's own updates.
What to do
Check whether your product depends on Fireworks AI. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 43m it lasted.
Anything that failed between 2026-11-15 02:30 UTC and 2026-11-15 03:13 UTC may need a replay.Subscribe to Fireworks AI's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=fireworks works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Fireworks AI 2
- investigating
We are seeing impacted performance for GLM 5.3. We are actively investigating.
provider
- resolved
We've resolved the incident and the affected service is now operational.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-d9bc509eb1
Is Fireworks AI still down?
No, this incident was resolved 2026-11-15 03:13 UTC. For Fireworks AI's live state, see https://down.guide/providers/fireworks.
How long did it last?
43m, from 2026-11-15 02:30 UTC to 2026-11-15 03:13 UTC, by the times Fireworks AI posted.
What caused it?
Fireworks AI hasn't published a root cause. If it does, it shows here.
Where does this come from?
Fireworks AI's official status page, https://status.fireworks.ai, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.