">
sevanalysis

Fireworks AI

AI. Source: Fireworks AI status page.

History starts 2026-10-12 12:33 UTC, the oldest incident this status page still shows. Figures for the last 90 days cover only the part since then.

Incidents, last 90 days
25+
Median duration
21m
p95 duration
2h 47m
Naming an upstream provider
0%
With a postmortem on the status page
0%

What failed, last 90 days

The text does not say enough to tell23
A provider or third-party service this vendor depends on failed2

Tagged by claude-haiku-5-5 from each incident's updates. See the methodology.

Incidents per month

Hatched months are before the recorded history starts.

All recorded incidents

Service Degradation for DeepSeek V4.1 Flash 1017 minor 2026-10-21 08:56 UTC 1h 2m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are seeing impacted performance for DeepSeek V4.1 Flash 1017. We are actively investigating.

  2. resolved

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

Excerpts are shortened. Read the full incident on Fireworks AI's status page.

Service Degradation for Deepseek V4.1 Flash minor 2026-10-21 05:28 UTC 30m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are seeing impacted performance for Deepseek V4.1 Flash. We are actively investigating.

  2. resolved

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

Excerpts are shortened. Read the full incident on Fireworks AI's status page.

Service Degradation for GLM 5.3 Flash minor 2026-10-21 01:14 UTC 6m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are seeing impacted performance for GLM 5.3 Flash. We are actively investigating.

  2. resolved

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

Excerpts are shortened. Read the full incident on Fireworks AI's status page.

Service Degradation for GLM 5.3 minor 2026-10-20 19:25 UTC 11m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are seeing impacted performance for GLM 5.3. We are actively investigating.

  2. resolved

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

Excerpts are shortened. Read the full incident on Fireworks AI's status page.

Service Degradation for Deepseek V4.1 Flash minor 2026-10-20 19:23 UTC 33m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are seeing impacted performance for Deepseek V4.1 Flash. We are actively investigating.

  2. resolved

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

Excerpts are shortened. Read the full incident on Fireworks AI's status page.

Service Degradation for Kimi K3 minor 2026-10-20 18:19 UTC 28m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

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

  2. resolved

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

Excerpts are shortened. Read the full incident on Fireworks AI's status page.

Elevated latency on some serverless models none 2026-10-20 01:29 UTC 1h 21m

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

  1. investigating

    Some serverless models are experiencing elevated response latency. We are investigating network degradation with one of our cloud service providers that is causing these delays.

  2. monitoring

    We are seeing recovery from the elevated response latency affecting some serverless models. We are monitoring to confirm that recovery is sustained.

  3. resolved

    The elevated response latency affecting some serverless models has been resolved. Response latency has returned to normal.

Excerpts are shortened. Read the full incident on Fireworks AI's status page.

Service Degradation for Qwen 3.8 Max minor 2026-10-19 23:05 UTC 18m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are seeing impacted performance for Qwen 3.8 Max. We are actively investigating.

  2. resolved

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

Excerpts are shortened. Read the full incident on Fireworks AI's status page.

Service Degradation for GLM 5.3 minor 2026-10-19 18:29 UTC 2h 41m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are seeing impacted performance for GLM 5.3. We are actively investigating.

  2. resolved

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

Excerpts are shortened. Read the full incident on Fireworks AI's status page.

Service Degradation for Kimi K3 minor 2026-10-19 01:08 UTC 17m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

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

  2. resolved

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

Excerpts are shortened. Read the full incident on Fireworks AI's status page.

Service Degradation for Qwen 3.8 Max minor 2026-10-18 06:59 UTC 21m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are seeing impacted performance for Qwen 3.8 Max. We are actively investigating.

  2. resolved

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

Excerpts are shortened. Read the full incident on Fireworks AI's status page.

Service Degradation for Qwen 3.8 Max minor 2026-10-18 03:16 UTC 16m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are seeing impacted performance for Qwen 3.8 Max. We are actively investigating.

  2. resolved

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

Excerpts are shortened. Read the full incident on Fireworks AI's status page.

Service Degradation for Qwen 3.8 Max minor 2026-10-17 08:22 UTC 32m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are seeing impacted performance for Qwen 3.8 Max. We are actively investigating.

  2. resolved

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

Excerpts are shortened. Read the full incident on Fireworks AI's status page.

Service Degradation for Qwen 3.8 Max minor 2026-10-17 07:22 UTC 15m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are seeing impacted performance for Qwen 3.8 Max. We are actively investigating.

  2. resolved

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

Excerpts are shortened. Read the full incident on Fireworks AI's status page.

Service Degradation for Kimi K3 minor 2026-10-15 08:48 UTC 17m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

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

  2. resolved

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

Excerpts are shortened. Read the full incident on Fireworks AI's status page.

Service Degradation for Qwen 3.8 Max minor 2026-10-15 08:09 UTC 1h 16m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are seeing impacted performance for Qwen 3.8 Max. We are actively investigating.

  2. resolved

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

Excerpts are shortened. Read the full incident on Fireworks AI's status page.

Service Degradation for Kimi K3 minor 2026-10-15 06:45 UTC 1h 20m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

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

  2. resolved

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

Excerpts are shortened. Read the full incident on Fireworks AI's status page.

CSP outage affecting multiple serverless models minor 2026-10-14 23:06 UTC 2h 47m

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

  1. investigating

    We are experiencing a cloud service provider (CSP) outage affecting multiple serverless models. Requests to affected models may fail. We are investigating the impact.

  2. monitoring

    Error rates for affected serverless models are beginning to recover. We are monitoring the recovery; some requests may still fail.

  3. monitoring

    We are starting to see recovery across the board. We are continuing to actively monitor the situation.

  4. resolved

    Service has been restored for all affected serverless models. This incident is resolved.

Excerpts are shortened. Read the full incident on Fireworks AI's status page.

Service Degradation for Deepseek V4.1 Flash minor 2026-10-14 22:33 UTC 13m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are seeing impacted performance for Deepseek V4.1 Flash. We are actively investigating.

  2. resolved

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

Excerpts are shortened. Read the full incident on Fireworks AI's status page.

Service Degradation for GLM 5.3 Fast minor 2026-10-14 21:24 UTC 2m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are seeing impacted performance for GLM 5.3 Fast. We are actively investigating.

  2. resolved

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

Excerpts are shortened. Read the full incident on Fireworks AI's status page.

Service Degradation for GLM 5.3 minor 2026-10-14 01:26 UTC 3m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are seeing impacted performance for GLM 5.3. We are actively investigating.

  2. resolved

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

Excerpts are shortened. Read the full incident on Fireworks AI's status page.

Service Degradation for GLM 5.3 minor 2026-10-13 09:37 UTC 3m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are seeing impacted performance for GLM 5.3. We are actively investigating.

  2. resolved

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

Excerpts are shortened. Read the full incident on Fireworks AI's status page.

Service Degradation for GLM 5.3 minor 2026-10-13 05:09 UTC 2h 45m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are seeing impacted performance for GLM 5.3. We are actively investigating.

  2. resolved

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

Excerpts are shortened. Read the full incident on Fireworks AI's status page.

Service Degradation for GLM 5.3 minor 2026-10-12 12:48 UTC 5h 18m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are seeing impacted performance for GLM 5.3. We are actively investigating.

  2. monitoring

    We have implemented a fix for the performance degradation affecting GLM 5.3 and are monitoring the results.

  3. resolved

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

Excerpts are shortened. Read the full incident on Fireworks AI's status page.

Service Degradation for GLM 5.3 minor 2026-10-12 12:33 UTC 0m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

    We are seeing impacted performance for GLM 5.3. We are actively investigating.

  2. resolved

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

Excerpts are shortened. Read the full incident on Fireworks AI's status page.