Scheduled maintenance: Serverless inference
We will be doing scheduled network maintenance with one of our North American infrastructure providers on Saturday, November 14, between 4:00 PM and 5:00 PM PT. The work will improve network stability. During this window, some serverless models may see a higher rate of errors (such as 503s), higher latency, or timeouts for several minutes. Where we can, we will send traffic to other regions. Requests to other models and regions should not be affected. We recommend retrying failed requests with exponential backoff. No other action is needed. We will post an update when the maintenance is complete.
The latest update from Fireworks AI.
State
Scheduled
Started
Ongoing for
3 h 55 min
Worst impact
Maintenance
Timeline
1 updateScheduled
3 h 55 min 100%
Updates
Times in UTCAs posted by Fireworks AI
We will be doing scheduled network maintenance with one of our North American infrastructure providers on Saturday, November 14, between 4:00 PM and 5:00 PM PT. The work will improve network stability. During this window, some serverless models may see a higher rate of errors (such as 503s), higher latency, or timeouts for several minutes. Where we can, we will send traffic to other regions. Requests to other models and regions should not be affected. We recommend retrying failed requests with exponential backoff. No other action is needed. We will post an update when the maintenance is complete.
Fireworks AI in the last 90 days
Full historyIncidents in 90 days
72
Days with an incident
21
Median duration
13 min
This incident
Not comparable
Other Fireworks AI incidents
All incidentsFireworks AI·Service Degradation for GLM 5.3 Flash
GLM 5.3 Flash had degraded performance for Fireworks AI. Fireworks AI reports that the incident is resolved. The outage lasted 11 minutes.
Fireworks AI·Service Degradation for Kimi K3 Fast
Fireworks AI reported degraded performance for Kimi K3 Fast. The incident is resolved. It lasted 6 minutes, from 14:15 to 14:21 UTC on 13 November 2026.
Fireworks AI·Service Degradation for DeepSeek V4.1 Flash 1017
DeepSeek V4.1 Flash 1017 had degraded performance for Fireworks AI. Fireworks AI investigated the issue. Fireworks AI resolved the incident at 11:56 UTC, and it lasted 44 minutes.
Fireworks AI·Service Degradation for GLM 5.3 Fast
Fireworks AI reports degraded performance for GLM 5.3 Fast. Fireworks AI investigated the problem. The incident is resolved and the affected service is operational. The outage lasted about 6 minutes.
Fireworks AI·Service Degradation for GLM 5.3
Fireworks AI reported degraded performance for GLM 5.3. Fireworks AI investigated the incident. The incident is resolved and the service is operational. It lasted 2 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.live/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.live/feed.xml?providers=fireworks/feed subscribe https://outages.live/feed.xml?providers=fireworksFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane