Snyk 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.
85.40%free of major or critical incidents, last 30 days
95.13%free of major or critical incidents, last 90 days
73.59%free of any incident, last 90 days
23incidents 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 29 min with any incident openAug 8 (UTC day): no vendor-reported incident openAug 9 (UTC day): no vendor-reported incident openAug 10 (UTC day): no vendor-reported incident openAug 11 (UTC day): 0 min with a major or critical incident open, 7 h 1 min with any incident open, 1 incident startedAug 12 (UTC day): no vendor-reported incident openAug 13 (UTC day): no vendor-reported incident openAug 14 (UTC day): no vendor-reported incident openAug 15 (UTC day): no vendor-reported incident openAug 16 (UTC day): no vendor-reported incident openAug 17 (UTC day): 0 min with a major or critical incident open, 4 h 41 min with any incident open, 1 incident startedAug 18 (UTC day): no vendor-reported incident openAug 19 (UTC day): no vendor-reported incident openAug 20 (UTC day): no vendor-reported incident openAug 21 (UTC day): no vendor-reported incident openAug 22 (UTC day): no vendor-reported incident openAug 23 (UTC day): no vendor-reported incident openAug 24 (UTC day): no vendor-reported incident openAug 25 (UTC day): no vendor-reported incident openAug 26 (UTC day): no vendor-reported incident openAug 27 (UTC day): no vendor-reported incident openAug 28 (UTC day): no vendor-reported incident openAug 29 (UTC day): no vendor-reported incident openAug 30 (UTC day): 0 min with a major or critical incident open, 10 h 40 min with any incident open, 2 incidents startedAug 31 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 1 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 2 (UTC day): 0 min with a major or critical incident open, 6 h 43 min with any incident openSep 3 (UTC day): no vendor-reported incident openSep 4 (UTC day): no vendor-reported incident openSep 5 (UTC day): no vendor-reported incident openSep 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): 0 min with a major or critical incident open, 2 h 25 min with any incident open, 1 incident startedSep 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): no vendor-reported incident openSep 16 (UTC day): no vendor-reported incident openSep 17 (UTC day): no vendor-reported incident openSep 18 (UTC day): 0 min with a major or critical incident open, 17 h 20 min with any incident open, 1 incident startedSep 19 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 20 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 21 (UTC day): 0 min with a major or critical incident open, 9 h 27 min with any incident open, 1 incident startedSep 22 (UTC day): no vendor-reported incident openSep 23 (UTC day): no vendor-reported incident openSep 24 (UTC day): no vendor-reported incident openSep 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): 0 min with a major or critical incident open, 13 h 58 min with any incident open, 2 incidents startedSep 29 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 30 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 1 (UTC day): 0 min with a major or critical incident open, 12 h 34 min with any incident openOct 2 (UTC day): no vendor-reported incident openOct 3 (UTC day): 0 min with a major or critical incident open, 4 h 11 min with any incident open, 1 incident startedOct 4 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 5 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 6 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 2 incidents startedOct 7 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedOct 8 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedOct 9 (UTC day): 0 min with a major or critical incident open, 7 h 9 min with any incident openOct 10 (UTC day): no vendor-reported incident openOct 11 (UTC day): no vendor-reported incident openOct 12 (UTC day): no vendor-reported incident openOct 13 (UTC day): 0 min with a major or critical incident open, 16 h 28 min with any incident open, 1 incident startedOct 14 (UTC day): 0 min with a major or critical incident open, 8 h 53 min with any incident openOct 15 (UTC day): 0 min with a major or critical incident open, 1 h 7 min with any incident open, 1 incident startedOct 16 (UTC day): no vendor-reported incident openOct 17 (UTC day): 0 min with a major or critical incident open, 22 h 16 min with any incident open, 1 incident startedOct 18 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 19 (UTC day): 0 min with a major or critical incident open, 22 h 3 min with any incident openOct 20 (UTC day): 0 min with a major or critical incident open, 2 h 58 min with any incident open, 1 incident startedOct 21 (UTC day): no vendor-reported incident openOct 22 (UTC day): 2 h 6 min with a major or critical incident open, 2 h 6 min with any incident open, 1 incident startedOct 23 (UTC day): 24 h with a major or critical incident open, 24 h with any incident open, 2 incidents startedOct 24 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openOct 25 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openOct 26 (UTC day): 9 h 41 min with a major or critical incident open, 9 h 41 min with any incident openOct 27 (UTC day): no vendor-reported incident openOct 28 (UTC day): no vendor-reported incident openOct 29 (UTC day): 3 h 32 min with a major or critical incident open, 3 h 32 min with any incident open, 1 incident startedOct 30 (UTC day): no vendor-reported incident openOct 31 (UTC day): no vendor-reported incident openNov 1 (UTC day): no vendor-reported incident openNov 2 (UTC day): 4 h 16 min with a major or critical incident open, 4 h 16 min with any incident open, 1 incident startedNov 3 (UTC day): 13 h 28 min with a major or critical incident open, 13 h 28 min with any 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 | 85.40% | 57.50% | 4.4 days | 12.7 days | 13 |
| Last 90 days | 95.13% | 73.59% | 4.4 days | 23.8 days | 23 |
This is what Snyk 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: Snyk status history · last 90 days · Snyk status page (opens in new tab) · Markdown