Jina 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
100%free of major or critical incidents, last 90 days
97.70%free of any incident, last 90 days
253incidents started, last 90 days
Last 90 days, by UTC day
Aug 7 (UTC day): no vendor-reported incident openAug 8 (UTC day): 0 min with a major or critical incident open, 5 min with any incident open, 1 incident startedAug 9 (UTC day): 0 min with a major or critical incident open, 6 min with any incident open, 1 incident startedAug 10 (UTC day): 0 min with a major or critical incident open, 10 min with any incident open, 1 incident startedAug 11 (UTC day): 0 min with a major or critical incident open, 5 min with any incident open, 1 incident startedAug 12 (UTC day): 0 min with a major or critical incident open, 1 h 55 min with any incident open, 4 incidents startedAug 13 (UTC day): 0 min with a major or critical incident open, 25 min with any incident open, 1 incident startedAug 14 (UTC day): 0 min with a major or critical incident open, 10 min with any incident open, 2 incidents startedAug 15 (UTC day): 0 min with a major or critical incident open, 10 min with any incident open, 2 incidents startedAug 16 (UTC day): no vendor-reported incident openAug 17 (UTC day): no vendor-reported incident openAug 18 (UTC day): 0 min with a major or critical incident open, 17 h 20 min with any incident open, 69 incidents startedAug 19 (UTC day): 0 min with a major or critical incident open, 2 h with any incident open, 12 incidents startedAug 20 (UTC day): 0 min with a major or critical incident open, 5 min with any incident open, 1 incident startedAug 21 (UTC day): 0 min with a major or critical incident open, 5 min with any incident open, 1 incident startedAug 22 (UTC day): no vendor-reported incident openAug 23 (UTC day): 0 min with a major or critical incident open, 5 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, 15 min with any incident open, 2 incidents startedAug 26 (UTC day): 0 min with a major or critical incident open, 1 h with any incident open, 3 incidents startedAug 27 (UTC day): 0 min with a major or critical incident open, 2 h with any incident open, 15 incidents startedAug 28 (UTC day): no vendor-reported incident openAug 29 (UTC day): 0 min with a major or critical incident open, 5 min with any incident open, 1 incident startedAug 30 (UTC day): no vendor-reported incident openAug 31 (UTC day): 0 min with a major or critical incident open, 5 min with any incident open, 1 incident startedSep 1 (UTC day): 0 min with a major or critical incident open, 50 min with any incident open, 5 incidents startedSep 2 (UTC day): 0 min with a major or critical incident open, 2 h 45 min with any incident open, 5 incidents startedSep 3 (UTC day): no vendor-reported incident openSep 4 (UTC day): 0 min with a major or critical incident open, 5 min with any incident open, 1 incident startedSep 5 (UTC day): no vendor-reported incident openSep 6 (UTC day): no vendor-reported incident openSep 7 (UTC day): 0 min with a major or critical incident open, 30 min with any incident open, 5 incidents startedSep 8 (UTC day): 0 min with a major or critical incident open, 25 min with any incident open, 5 incidents startedSep 9 (UTC day): 0 min with a major or critical incident open, 11 min with any incident open, 2 incidents startedSep 10 (UTC day): 0 min with a major or critical incident open, 10 min with any incident open, 2 incidents startedSep 11 (UTC day): no vendor-reported incident openSep 12 (UTC day): 0 min with a major or critical incident open, 25 min with any incident open, 2 incidents startedSep 13 (UTC day): 0 min with a major or critical incident open, 4 h with any incident open, 1 incident startedSep 14 (UTC day): no vendor-reported incident openSep 15 (UTC day): 0 min with a major or critical incident open, 40 min with any incident open, 7 incidents startedSep 16 (UTC day): no vendor-reported incident openSep 17 (UTC day): 0 min with a major or critical incident open, 30 min with any incident open, 3 incidents startedSep 18 (UTC day): 0 min with a major or critical incident open, 25 min with any incident open, 2 incidents startedSep 19 (UTC day): no vendor-reported incident openSep 20 (UTC day): no vendor-reported incident openSep 21 (UTC day): 0 min with a major or critical incident open, 35 min with any incident open, 3 incidents startedSep 22 (UTC day): no vendor-reported incident openSep 23 (UTC day): 0 min with a major or critical incident open, 10 min with any incident open, 2 incidents startedSep 24 (UTC day): 0 min with a major or critical incident open, 5 min with any incident open, 1 incident startedSep 25 (UTC day): 0 min with a major or critical incident open, 5 min with any incident open, 1 incident startedSep 26 (UTC day): 0 min with a major or critical incident open, 55 min with any incident open, 2 incidents startedSep 27 (UTC day): no vendor-reported incident openSep 28 (UTC day): no vendor-reported incident openSep 29 (UTC day): 0 min with a major or critical incident open, 10 min with any incident open, 2 incidents startedSep 30 (UTC day): 0 min with a major or critical incident open, 5 min with any incident open, 1 incident startedOct 1 (UTC day): 0 min with a major or critical incident open, 25 min with any incident open, 4 incidents startedOct 2 (UTC day): no vendor-reported incident openOct 3 (UTC day): 0 min with a major or critical incident open, 5 min with any incident open, 1 incident startedOct 4 (UTC day): 0 min with a major or critical incident open, 35 min with any incident open, 4 incidents startedOct 5 (UTC day): 0 min with a major or critical incident open, 25 min with any incident open, 1 incident startedOct 6 (UTC day): 0 min with a major or critical incident open, 30 min with any incident open, 4 incidents startedOct 7 (UTC day): no vendor-reported incident openOct 8 (UTC day): 0 min with a major or critical incident open, 10 min with any incident open, 2 incidents startedOct 9 (UTC day): 0 min with a major or critical incident open, 15 min with any incident open, 2 incidents startedOct 10 (UTC day): 0 min with a major or critical incident open, 5 min with any incident open, 1 incident startedOct 11 (UTC day): no vendor-reported incident openOct 12 (UTC day): no vendor-reported incident openOct 13 (UTC day): no vendor-reported incident openOct 14 (UTC day): 0 min with a major or critical incident open, 5 min with any incident open, 1 incident startedOct 15 (UTC day): 0 min with a major or critical incident open, 25 min with any incident open, 2 incidents startedOct 16 (UTC day): 0 min with a major or critical incident open, 20 min with any incident open, 3 incidents startedOct 17 (UTC day): 0 min with a major or critical incident open, 25 min with any incident open, 2 incidents startedOct 18 (UTC day): 0 min with a major or critical incident open, 1 h with any incident open, 2 incidents startedOct 19 (UTC day): 0 min with a major or critical incident open, 14 min with any incident open, 3 incidents startedOct 20 (UTC day): 0 min with a major or critical incident open, 5 min with any incident open, 1 incident startedOct 21 (UTC day): 0 min with a major or critical incident open, 1 h 20 min with any incident open, 14 incidents startedOct 22 (UTC day): 0 min with a major or critical incident open, 1 h 35 min with any incident open, 16 incidents startedOct 23 (UTC day): no vendor-reported incident openOct 24 (UTC day): 0 min with a major or critical incident open, 10 min with any incident open, 1 incident startedOct 25 (UTC day): no vendor-reported incident openOct 26 (UTC day): 0 min with a major or critical incident open, 5 min with any incident open, 1 incident startedOct 27 (UTC day): no vendor-reported incident openOct 28 (UTC day): 0 min with a major or critical incident open, 25 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, 10 min with any incident open, 2 incidents startedOct 31 (UTC day): 0 min with a major or critical incident open, 5 min with any incident open, 1 incident startedNov 1 (UTC day): 0 min with a major or critical incident open, 1 h 14 min with any incident open, 7 incidents startedNov 2 (UTC day): 0 min with a major or critical incident open, 20 min with any incident open, 2 incidents startedNov 3 (UTC day): no vendor-reported incident openNov 4 (UTC day): no vendor-reported 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% | 98.69% | 0 min | 9 h 23 min | 73 |
| Last 90 days | 100% | 97.70% | 0 min | 2.1 days | 253 |
This is what Jina 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: Jina AI status history · last 90 days · Jina AI status page (opens in new tab) · Markdown