Service Degradation for GLM 5.3 Fast
Fireworks AI reports performance problems with GLM 5.3 Fast. Fireworks AI reports that the incident is resolved. The outage lasted about 13 minutes.
State
Resolved
Started
Lasted
13 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
13 min 100%
Updates
Times in UTCAs posted by Fireworks AI
We've resolved the incident and the affected service is now operational.
We are seeing impacted performance for GLM 5.3 Fast. We are actively investigating.
Fireworks AI in the last 90 days
Full historyIncidents in 90 days
46
Days with an incident
14
Median duration
10 min
This incident
1.3× the median
Other Fireworks AI incidents
All incidentsFireworks AI·Service Degradation for Muse Spark Open US
Fireworks AI reports degraded performance for Muse Spark Open US. Fireworks AI resolved the incident, and the affected service is now operational. The outage lasted about 4 minutes.
Fireworks AI·Service Degradation for Muse Spark Open US
Fireworks AI reports degraded service for Muse Spark Open US. Fireworks AI resolved the incident and the service is now operational. The outage lasted about 3 minutes.
Fireworks AI·Service Degradation for Muse Spark Open US
Fireworks AI reported degraded performance for Muse Spark Open US. Fireworks AI investigated the issue and later resolved it. The incident lasted about 10 minutes.
Fireworks AI·Service Degradation for MiniMax M3.1 Flash
Fireworks AI reports degraded performance for MiniMax M3.1 Flash. Fireworks AI investigated the incident. The incident is resolved and lasted about 5 minutes.
Fireworks AI·Service Degradation for Deepseek V4.1 Flash US
Deepseek V4.1 Flash US had degraded performance. Fireworks AI reports that the incident is resolved and that the service is now operational. The incident lasted 3 minutes.
Follow Fireworks AI
Your coding agent knows when Fireworks AI is down, and tells you when a failure is theirs, not yours. You can also get Fireworks AI incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "fireworks" and tell me if Fireworks AI has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=fireworks/feed subscribe https://outages.cc/feed.xml?providers=fireworksFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane