Live

Service Degradation for Muse Spark Open US

0

Muse Spark Open US had degraded performance. Fireworks AI investigated the problem. The incident is resolved and lasted 14 minutes.

A language model wrote this summary from the updates of Fireworks AI.

State

Resolved

Started

4 h ago

2026-10-31 23:43 UTC

Lasted

14 min

until 2026-10-31 23:57 UTC

Worst impact

Degraded

Timeline

2 updates
23:4323:4623:5023:5323:57
DegradedUpdate postedTimes in UTC

Investigating

14 min 100%

Updates

Times in UTC

As posted by Fireworks AI

Resolved2026-10-31 23:57 UTC
Investigating2026-10-31 23:45 UTC

We are seeing impacted performance for Muse Spark Open US. We are actively investigating.

Fireworks AI in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

2

Days with an incident

3

Median duration

14 min

This incident

About the median

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

31 h 18 min
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.cc/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.cc/feed.xml?providers=fireworks
Slack
/feed subscribe https://outages.cc/feed.xml?providers=fireworks

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane