CompaniesFireworks AIUptime
Fireworks AI uptime
From vendor reports Derived from the incidents the vendor posted on its own status page, not measured by us. A minute counts as an outage minute when a major or critical incident (as the vendor labelled it) was open; incident minutes include minor ones too. Maintenance and incidents marked "no impact" are left out, overlapping incidents are merged, a resolved incident counts for at most 7 days, and one still open with no resolution counts for at most 24 hours.
100%free of major or critical incidents, last 30 days
97.79%free of major or critical incidents, last 90 days
92.79%free of any incident, last 90 days
141incidents started, last 90 days
Last 90 days, by UTC day
Aug 7 (UTC day): 0 min with a major or critical incident open, 7 h 19 min with any incident open, 4 incidents startedAug 8 (UTC day): no vendor-reported incident openAug 9 (UTC day): no vendor-reported incident openAug 10 (UTC day): 0 min with a major or critical incident open, 23 min with any incident open, 1 incident startedAug 11 (UTC day): 6 h 44 min with a major or critical incident open, 6 h 44 min with any incident open, 3 incidents startedAug 12 (UTC day): 24 h with a major or critical incident open, 24 h with any incident open, 2 incidents startedAug 13 (UTC day): 15 h 51 min with a major or critical incident open, 21 h 8 min with any incident open, 1 incident startedAug 14 (UTC day): 0 min with a major or critical incident open, 1 h 37 min with any incident open, 7 incidents startedAug 15 (UTC day): no vendor-reported incident openAug 16 (UTC day): 0 min with a major or critical incident open, 33 min with any incident open, 3 incidents startedAug 17 (UTC day): 0 min with a major or critical incident open, 15 min with any incident open, 3 incidents startedAug 18 (UTC day): 1 h 9 min with a major or critical incident open, 1 h 41 min with any incident open, 3 incidents startedAug 19 (UTC day): 0 min with a major or critical incident open, 26 min with any incident open, 2 incidents startedAug 20 (UTC day): no vendor-reported incident openAug 21 (UTC day): 0 min with a major or critical incident open, 2 h 22 min with any incident open, 9 incidents startedAug 22 (UTC day): no vendor-reported incident openAug 23 (UTC day): 0 min with a major or critical incident open, 4 min with any incident open, 1 incident startedAug 24 (UTC day): no vendor-reported incident openAug 25 (UTC day): 0 min with a major or critical incident open, 1 h 18 min with any incident open, 4 incidents startedAug 26 (UTC day): 0 min with a major or critical incident open, 24 min with any incident open, 1 incident startedAug 27 (UTC day): no vendor-reported incident openAug 28 (UTC day): 0 min with a major or critical incident open, 14 min with any incident open, 2 incidents startedAug 29 (UTC day): no vendor-reported incident openAug 30 (UTC day): no vendor-reported incident openAug 31 (UTC day): 0 min with a major or critical incident open, 13 min with any incident open, 1 incident startedSep 1 (UTC day): 0 min with a major or critical incident open, 5 h 58 min with any incident open, 4 incidents startedSep 2 (UTC day): no vendor-reported incident openSep 3 (UTC day): no vendor-reported incident openSep 4 (UTC day): no vendor-reported incident openSep 5 (UTC day): 0 min with a major or critical incident open, 1 min with any incident open, 1 incident startedSep 6 (UTC day): no vendor-reported incident openSep 7 (UTC day): no vendor-reported incident openSep 8 (UTC day): no vendor-reported incident openSep 9 (UTC day): no vendor-reported incident openSep 10 (UTC day): no vendor-reported incident openSep 11 (UTC day): no vendor-reported incident openSep 12 (UTC day): no vendor-reported incident openSep 13 (UTC day): no vendor-reported incident openSep 14 (UTC day): no vendor-reported incident openSep 15 (UTC day): 0 min with a major or critical incident open, 1 h 14 min with any incident open, 2 incidents startedSep 16 (UTC day): no vendor-reported incident openSep 17 (UTC day): no vendor-reported incident openSep 18 (UTC day): no vendor-reported incident openSep 19 (UTC day): 0 min with a major or critical incident open, 21 min with any incident open, 3 incidents startedSep 20 (UTC day): no vendor-reported incident openSep 21 (UTC day): 0 min with a major or critical incident open, 7 min with any incident open, 1 incident startedSep 22 (UTC day): 0 min with a major or critical incident open, 1 min with any incident openSep 23 (UTC day): no vendor-reported incident openSep 24 (UTC day): 0 min with a major or critical incident open, 40 min with any incident open, 3 incidents startedSep 25 (UTC day): no vendor-reported incident openSep 26 (UTC day): no vendor-reported incident openSep 27 (UTC day): no vendor-reported incident openSep 28 (UTC day): no vendor-reported incident openSep 29 (UTC day): no vendor-reported incident openSep 30 (UTC day): no vendor-reported incident openOct 1 (UTC day): 0 min with a major or critical incident open, 8 min with any incident open, 1 incident startedOct 2 (UTC day): 0 min with a major or critical incident open, 14 min with any incident open, 1 incident startedOct 3 (UTC day): no vendor-reported incident openOct 4 (UTC day): no vendor-reported incident openOct 5 (UTC day): 0 min with a major or critical incident open, 54 min with any incident open, 4 incidents startedOct 6 (UTC day): 0 min with a major or critical incident open, 2 h 12 min with any incident open, 1 incident startedOct 7 (UTC day): 0 min with a major or critical incident open, 22 min with any incident open, 2 incidents startedOct 8 (UTC day): 0 min with a major or critical incident open, 2 h with any incident open, 2 incidents startedOct 9 (UTC day): no vendor-reported incident openOct 10 (UTC day): 0 min with a major or critical incident open, 1 h 48 min with any incident open, 2 incidents startedOct 11 (UTC day): 0 min with a major or critical incident open, 31 min with any incident open, 1 incident startedOct 12 (UTC day): 0 min with a major or critical incident open, 5 h 52 min with any incident open, 5 incidents startedOct 13 (UTC day): 0 min with a major or critical incident open, 2 h 48 min with any incident open, 2 incidents startedOct 14 (UTC day): 0 min with a major or critical incident open, 1 h 13 min with any incident open, 4 incidents startedOct 15 (UTC day): 0 min with a major or critical incident open, 4 h 29 min with any incident open, 3 incidents startedOct 16 (UTC day): no vendor-reported incident openOct 17 (UTC day): 0 min with a major or critical incident open, 47 min with any incident open, 2 incidents startedOct 18 (UTC day): 0 min with a major or critical incident open, 38 min with any incident open, 2 incidents startedOct 19 (UTC day): 0 min with a major or critical incident open, 5 h 48 min with any incident open, 4 incidents startedOct 20 (UTC day): 0 min with a major or critical incident open, 20 h 12 min with any incident open, 3 incidents startedOct 21 (UTC day): 0 min with a major or critical incident open, 1 h 38 min with any incident open, 3 incidents startedOct 22 (UTC day): 0 min with a major or critical incident open, 1 h 25 min with any incident open, 6 incidents startedOct 23 (UTC day): 0 min with a major or critical incident open, 3 h 5 min with any incident open, 1 incident startedOct 24 (UTC day): no vendor-reported incident openOct 25 (UTC day): 0 min with a major or critical incident open, 4 min with any incident open, 1 incident startedOct 26 (UTC day): 0 min with a major or critical incident open, 3 h 26 min with any incident open, 6 incidents startedOct 27 (UTC day): 0 min with a major or critical incident open, 54 min with any incident open, 2 incidents startedOct 28 (UTC day): 0 min with a major or critical incident open, 1 h 15 min with any incident open, 5 incidents startedOct 29 (UTC day): no vendor-reported incident openOct 30 (UTC day): 0 min with a major or critical incident open, 1 h 8 min with any incident open, 2 incidents startedOct 31 (UTC day): 0 min with a major or critical incident open, 19 min with any incident open, 2 incidents startedNov 1 (UTC day): no vendor-reported incident openNov 2 (UTC day): 0 min with a major or critical incident open, 5 min with any incident open, 1 incident startedNov 3 (UTC day): 0 min with a major or critical incident open, 15 h 16 min with any incident open, 10 incidents startedNov 4 (UTC day): 0 min with a major or critical incident open, 6 min with any incident open
Aug 7today
no incident minor incident minor, 6 h+ major/critical major/critical, 6 h+ before archive
Last 7 days, by hour
now
Numbers
| Window | Free of major/critical | Free of any incident | Outage time | Incident time | Incidents |
|---|---|---|---|---|---|
| Last 30 days | 100% | 89.13% | 0 min | 3.3 days | 76 |
| Last 90 days | 97.79% | 92.79% | 47 h 44 min | 6.5 days | 141 |
This is what Fireworks AI itself reported, so it can miss outages the vendor never posted and overstate ones where an incident was left open. Regional or single-component incidents count the same as global ones. Recomputed .
See the incidents: Fireworks AI status history · last 90 days · Fireworks AI status page (opens in new tab) · Markdown