Service Degradation for Kimi K3.1 Pro
Fireworks AI reports degraded performance for Kimi K3.1 Pro. Fireworks AI investigated the incident and later reported that the service is operational. Fireworks AI resolved the incident after 3 minutes.
State
Resolved
Started
Lasted
3 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
3 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 Kimi K3.1 Pro. We are actively investigating.
Fireworks AI in the last 90 days
Full historyIncidents in 90 days
59
Days with an incident
19
Median duration
11 min
This incident
73% shorter than the median
Other Fireworks AI incidents
All incidentsFireworks AI·Service Degradation for Kimi K3.1 Pro
Kimi K3.1 Pro gives degraded performance. Fireworks AI reports that the problem is under investigation.
Fireworks AI·Service Degradation for GLM 5.3
GLM 5.3 had degraded performance on Fireworks AI. Fireworks AI reports that this incident is resolved. It lasted 24 minutes.
Fireworks AI·Service Degradation for DeepSeek V4.1 Flash 1017
DeepSeek V4.1 Flash 1017 had degraded performance for some users. Fireworks AI investigated the incident and later reported that the service is operational. The outage is resolved and it lasted 85 minutes.
Fireworks AI·Service Degradation for Kimi K3
Fireworks AI reports degraded performance for Kimi K3. Fireworks AI says the incident is resolved. The outage lasted 12 hours and 5 minutes.
Fireworks AI·Service Degradation for Kimi K3 US
Fireworks AI reported degraded performance for Kimi K3 US. Fireworks AI resolved the incident, and the service is operational. The outage lasted 66 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