Fireworks AI reported "Service Degradation for Kimi K3" on its status page at 2026-11-10 06:01 UTC. Kimi K3 shows degraded performance. Fireworks AI reports that it is investigating the problem.

Fireworks AI did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-11-10 06:01 UTC. This page shows the end time when Fireworks AI marks it resolved.

How do I get alerts for Fireworks AI?

Subscribe to the Fireworks AI live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Fireworks AI. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

Fireworks AIIncident ·

Service Degradation for Kimi K3

DegradedOfficial update

Kimi K3 shows degraded performance. Fireworks AI reports that it is investigating the problem.

State

Investigating

Started

Ongoing for

50 min

Worst impact

Degraded

Timeline

1 update

06:0106:1306:2606:3806:51

DegradedUpdate postedTimes in UTC

Investigating

50 min 100%

Updates

Times in UTC

As posted by Fireworks AI

Investigating

We are seeing impacted performance for Kimi K3. We are actively investigating.

Fireworks AI in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

10 min

This incident

5.0× the median

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

10 days

median 10 min

90 days agoToday

Other Fireworks AI incidents

All incidents

Fireworks AI·Service Degradation for Kimi K3 US

Kimi K3 US shows degraded performance. Fireworks AI reports that the incident started at 05:50 UTC on 10 November 2026. Fireworks AI is investigating.

Degraded

Fireworks AI·Service Degradation for Qwen 3.8 Max

Fireworks AI reported degraded performance for Qwen 3.8 Max. Fireworks AI investigated the problem and then stated that the incident is resolved. The degradation lasted about 3 minutes, from 02:39 to 02:42 UTC on 2026-11-08.

Resolved

Fireworks AI·Service Degradation for GLM 5.3 Fast

Fireworks AI reports degraded performance for GLM 5.3 Fast. Fireworks AI resolved the incident and the service is now operational. The incident lasted about 14 minutes.

Resolved

Fireworks AI·Service Degradation for GLM 5.3 Fast

Fireworks AI reports degraded performance for GLM 5.3 Fast. Fireworks AI resolved the incident and the service operates again. The outage lasted about 10 minutes.

Resolved

Fireworks AI·Service Degradation for GLM 5.3 Flash US

Fireworks AI reports degraded performance for GLM 5.3 Flash US. The incident is resolved and the service is operational. The outage lasted 24 minutes.

Resolved

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