Fireworks AI reported "Service Degradation for GLM 5.3 Flash" on its status page at 2026-10-27 12:26 UTC.

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-10-27 12:26 UTC and ended at 2026-10-27 12:50 UTC. It lasted 24 min.

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.

Fireworks AIIncident · 2026-10-27 12:26 UTC

Service Degradation for GLM 5.3 Flash

ResolvedOfficial update

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

The latest update from Fireworks AI.

State

Resolved

Started

5 d ago

2026-10-27 12:26 UTC

Lasted

24 min

until 2026-10-27 12:50 UTC

Worst impact

Degraded

Timeline

2 updates

12:2612:3212:3812:4412:50

DegradedUpdate postedTimes in UTC

Investigating

24 min 100%

Updates

Times in UTC

As posted by Fireworks AI

Resolved2026-10-27 12:50 UTC

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

Investigating2026-10-27 12:26 UTC

We are seeing impacted performance for GLM 5.3 Flash. 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

11 min

This incident

2.2× the median

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

36 h 57 min

median 11 min

90 days agoToday

Other Fireworks AI incidents

All incidents

Fireworks AI·Service Degradation for Muse Spark Open US

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

Resolvedresolved 10 h ago

Fireworks AI·Service Degradation for Kimi K3

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

Resolvedresolved 15 h ago

Fireworks AI·Service degradation

Fireworks AI reports service degradation that affects deployment creation, dedicated training, and batch inference services. Fireworks AI identified the problem and continues to work on a fix. The outage started on 30 October 2026 and is not resolved.

Noticeupdated 2 d ago

Fireworks AI·Service Degradation for Qwen 3.8 Max

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

Resolvedresolved 2 d ago

Fireworks AI·Service Degradation for Qwen 3.8 Max

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

Resolvedresolved 2 d ago

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