outages.live
Live

Fireworks AI

Fireworks AI is operational

Checked 15 s ago Operational

Service degradation

Fireworks AI reports service degradation that affects deployment creation, dedicated training, and batch inference services. Fireworks AI has identified the problem and is working to resolve it.

Noticeupdated 2 d ago

History

90 days agoToday

Incidents in 90 days

25

Days with an incident

10

Median duration

11 min

Longest incident

3 h 5 min

Components

22
MiniMax M3.1 Flash Operational
90 days agoNo incidentsToday
DeepSeek V4.1 Flash 1017 Operational
90 days agoNo incidentsToday
DeepSeek V4.1 Flash 1017 US Operational
90 days agoNo incidentsToday
Muse Spark Open US Operational
90 days agoNo incidentsToday
GLM 5.3 Flash Operational
90 days agoNo incidentsToday
GLM 5.3 Flash US Operational
90 days agoNo incidentsToday
GLM 5.3 Operational
90 days agoNo incidentsToday
GLM 5.3 Fast Operational
90 days agoNo incidentsToday
GLM 5.3 US Operational
90 days agoNo incidentsToday
Ember-1 Operational
90 days agoNo incidentsToday
Kimi K3 US Operational
90 days agoNo incidentsToday
Kimi K3 Fast Operational
90 days agoNo incidentsToday
Kimi K3 Operational
90 days agoNo incidentsToday
Qwen 3.8 Max Operational
90 days agoNo incidentsToday
Deepseek V4.1 Flash Operational
90 days agoNo incidentsToday
Deepseek V4.1 Flash US Operational
90 days agoNo incidentsToday
Nemotron 3 Ultra US Operational
90 days agoNo incidentsToday
Nemotron 3.5 Lightning US Operational
90 days agoNo incidentsToday
Minimax M3 US Operational
90 days agoNo incidentsToday
MiniMax M3 Operational
90 days agoNo incidentsToday
Inkling Operational
90 days agoNo incidentsToday
GPT-OSS 120B Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 31, 2026

Duration13 min23:43 to 23:56Service Degradation for Muse Spark Open USDegraded

We've resolved the incident and the affected service is now operational.

Duration5 min18:21 to 18:26Service Degradation for Kimi K3Degraded

We've resolved the incident and the affected service is now operational.

Oct 30, 2026

Duration36 min19:37 to 20:13Service Degradation for Qwen 3.8 MaxDegraded

We've resolved the incident and the affected service is now operational.

Duration32 min10:28 to 11:00Service Degradation for Qwen 3.8 MaxDegraded

We've resolved the incident and the affected service is now operational.

Oct 28, 2026

Duration8 min15:08 to 15:16Service Degradation for GLM 5.3 FlashDegraded

We've resolved the incident and the affected service is now operational.

Duration57 min07:13 to 08:10Service Degradation for GLM 5.3 FlashDegraded

We've resolved the incident and the affected service is now operational.

Duration2 min05:56 to 05:58Service Degradation for MiniMax M3.1 FlashDegraded

We've resolved the incident and the affected service is now operational.

Duration3 min05:45 to 05:48Service Degradation for MiniMax M3.1 FlashDegraded

We've resolved the incident and the affected service is now operational.

Duration4 min05:35 to 05:39Service Degradation for MiniMax M3.1 FlashDegraded

We've resolved the incident and the affected service is now operational.

Oct 27, 2026

Duration24 min12:26 to 12:50Service Degradation for GLM 5.3 FlashDegraded

We've resolved the incident and the affected service is now operational.

Duration30 min01:07 to 01:37Service Degradation for Kimi K3Degraded

We've resolved the incident and the affected service is now operational.

Oct 26, 2026

Duration7 min23:49 to 23:56Service Degradation for Kimi K3Degraded

We've resolved the incident and the affected service is now operational.

Duration23 min23:03 to 23:26Service Degradation for GLM 5.3 FlashDegraded

We've resolved the incident and the affected service is now operational.

Duration2 h 34 min19:47 to 22:21Service Degradation for Kimi K3Degraded

We've resolved the incident and the affected service is now operational.

Duration1 min19:43 to 19:44Service Degradation for MiniMax M3.1 FlashDegraded

We've resolved the incident and the affected service is now operational.

Duration7 min18:40 to 18:47Service Degradation for Kimi K3Degraded

We've resolved the incident and the affected service is now operational.

Duration14 min17:59 to 18:13Service Degradation for Kimi K3Degraded

We've resolved the incident and the affected service is now operational.

Oct 25, 2026

Duration4 min23:29 to 23:33Service Degradation for GLM 5.3Degraded

We've resolved the incident and the affected service is now operational.

Oct 23, 2026

Duration3 h 5 min13:33 to 16:38Service Degradation for GLM 5.3Degraded

We've resolved the incident and the affected service is now operational.

Oct 22, 2026

Duration1 min22:05 to 22:06Service Degradation for DeepSeek V4.1 Flash 1017Degraded

We've resolved the incident and the affected service is now operational.

Duration1 min20:52 to 20:53Service Degradation for DeepSeek V4.1 Flash 1017Degraded

We've resolved the incident and the affected service is now operational.

Duration25 min17:26 to 17:50Service Degradation for DeepSeek V4.1 Flash 1017Degraded

We've resolved the incident and the affected service is now operational.

Duration1 min02:04 to 02:05Service Degradation for Deepseek V4.1 FlashDegraded

We've resolved the incident and the affected service is now operational.

Duration56 min00:34 to 01:30Service Degradation for Deepseek V4.1 FlashDegraded

We've resolved the incident and the affected service is now operational.

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane