Fireworks AI status — and how to poll it yourself

At this snapshot, 9 of the 9 providers on our status board reported fully operational. Here is where Fireworks AI stood, and how to get the same answer from its status API without a browser.

The 22 components Fireworks AI reports status for

When Fireworks AI says "operational", this is the granularity behind the claim — the component list its own status feed publishes, fetched 2026-11-02. All were reported operational at snapshot time. If an incident hits, these are the names its status page will scope it to.

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

Polling Fireworks AI's status programmatically

Atlassian Statuspage v2. GET /api/v2/status.json returns status.indicator (none | minor | major | critical) and a human description; GET /api/v2/components.json returns per-component state.

curl -s https://status.fireworks.ai/api/v2/status.json

Gotcha (verified 2026-11-02): Migrated from BetterStack to Atlassian Statuspage (observed 2026-08-06): /index.json now returns 404; use /api/v2/status.json + /api/v2/components.json

Everything above was verified against the live endpoint on 2026-11-02 — nothing is inferred from platform defaults. If the endpoint moved, tell us.

Model retirements — Fireworks AI

Our 129-row deprecations table tracks the providers that publish dated, citable retirement schedules (OpenAI, Anthropic, Google Vertex AI and Azure OpenAI). Fireworks AI publishes no dated model-retirement schedule we could verify against its own docs — absence here means absence of a published schedule, not a no-deprecation guarantee. Pin model versions and watch the provider's changelog either way.

Other providers