CheckUpstream measured Fireworks AI at 100.000% availability across 2034 independent checks (global · api). 113 incidents were recorded in the past 12 months; the most recent resolved earlier today after 24 minutes. Status signals are polled from Fireworks AI's official incident.io status page, alongside independent probes and community reports.
30 days measured availability how this is computed
100.000%
global · api · n=2034 · p95 220ms (30d)
Share of our own checks against Fireworks AI endpoints that returned Fireworks AI's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 5 incidents · 29 of 30 days with none posted · 59m of declared impact
1 of 232 tracked services had more incidents in the last 30 days.
Share of each window with no impact declared by Fireworks AI
7d
99.614%
30d
99.863%
90d
99.910%
180d
99.955%
1y
99.978%
Downtime like this can be refundable
If you're a paying Fireworks AI customer, outages in these windows may count against Fireworks AI's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Fireworks AI entitlement →Does Fireworks AI actually matter to you?
A Fireworks AI outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 5 incidents Fireworks AI published and resolved in the last 30 days, measured between their own start and resolution times. It describes how long Fireworks AI takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Sep 1, 01:41 UTC · resolved in 23m · Resolved
Aug 28, 19:25 UTC · resolved in 25m · Resolved
Aug 28, 14:25 UTC · resolved in 20m · Resolved
Aug 24, 13:14 UTC · resolved in 20m · Resolved
Live Fireworks AI status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/fireworks-ai)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Fireworks AI is currently Operational. CheckUpstream tracks Fireworks AI in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Looking for the live "is Fireworks AI down" view? See the Fireworks AI Live status page.
Aug 16, 15:53 UTC · resolved in 47m · Resolved
Jul 31, 18:36 UTC · resolved in 49m · Resolved
Jul 31, 14:21 UTC · resolved in 33m · Resolved
Jul 31, 13:21 UTC · resolved in 13m · Resolved
Fireworks AI's last resolved incident started earlier today and lasted 23 minutes (degraded performance).
Fireworks AI's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Fireworks AI endpoints. It is the share of checks that returned the expected response, not a figure taken from Fireworks AI's status page.
Sign up to CheckUpstream and add Fireworks AI to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Fireworks AI's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.