Live

Service Outage for Kimi K3.1 Pro

Major outageOfficial update
0

Kimi K3.1 Pro does not work and has a major outage. Fireworks AI says it is investigating. Fireworks AI reports that it has partially restored service to Kimi K3.1 Pro.

State

Investigating

Started

Ongoing for

41 min

Worst impact

Major outage

Timeline

2 updates
01:1201:2201:3201:4201:53
Major outageUpdate postedTimes in UTC

Investigating

41 min 100%

Updates

Times in UTC

As posted by Fireworks AI

Investigating

We’ve partially restored service to Kimi K3.1 Pro, and are still actively root causing the situation

Investigating

We are actively investigating an outage for Kimi K3.1 Pro

Fireworks AI in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

78

Days with an incident

25

Median duration

14 min

This incident

3.0× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

13 days
median 14 min
90 days agoToday

Other Fireworks AI incidents

All incidents

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=fireworks
Slack
/feed subscribe https://outages.live/feed.xml?providers=fireworks

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane