Semgrep 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.
99.96%free of major or critical incidents, last 30 days
99.65%free of major or critical incidents, last 90 days
99.25%free of any incident, last 90 days
12incidents started, last 90 days
Last 90 days, by UTC day
Aug 7 (UTC day): no vendor-reported 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): no vendor-reported incident openAug 12 (UTC day): 2 h 47 min with a major or critical incident open, 2 h 47 min with any incident open, 1 incident startedAug 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): no vendor-reported incident openAug 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): 2 h 40 min with a major or critical incident open, 2 h 40 min with any incident open, 1 incident startedAug 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): no vendor-reported incident openAug 31 (UTC day): no vendor-reported incident openSep 1 (UTC day): no vendor-reported incident openSep 2 (UTC day): no vendor-reported incident openSep 3 (UTC day): 1 h 10 min with a major or critical incident open, 1 h 10 min with any incident open, 1 incident startedSep 4 (UTC day): 25 min with a major or critical incident open, 25 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): 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): 0 min with a major or critical incident open, 1 h 10 min with any incident open, 1 incident startedSep 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): no vendor-reported incident openSep 19 (UTC day): no vendor-reported incident openSep 20 (UTC day): no vendor-reported incident openSep 21 (UTC day): no vendor-reported incident openSep 22 (UTC day): 13 min with a major or critical incident open, 13 min with any incident open, 1 incident startedSep 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): no vendor-reported incident openSep 29 (UTC day): no vendor-reported incident openSep 30 (UTC day): no vendor-reported incident openOct 1 (UTC day): no vendor-reported incident openOct 2 (UTC day): no vendor-reported incident openOct 3 (UTC day): no vendor-reported incident openOct 4 (UTC day): no vendor-reported incident openOct 5 (UTC day): 14 min with a major or critical incident open, 14 min with any incident open, 1 incident startedOct 6 (UTC day): no vendor-reported incident openOct 7 (UTC day): no vendor-reported incident openOct 8 (UTC day): no vendor-reported incident openOct 9 (UTC day): no vendor-reported 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): no vendor-reported incident openOct 14 (UTC day): no vendor-reported incident openOct 15 (UTC day): 0 min with a major or critical incident open, 1 h 18 min with any incident open, 1 incident startedOct 16 (UTC day): no vendor-reported incident openOct 17 (UTC day): no vendor-reported incident openOct 18 (UTC day): no vendor-reported incident openOct 19 (UTC day): 0 min with a major or critical incident open, 2 h 49 min with any incident open, 1 incident startedOct 20 (UTC day): no vendor-reported incident openOct 21 (UTC day): no vendor-reported incident openOct 22 (UTC day): no vendor-reported incident openOct 23 (UTC day): no vendor-reported incident openOct 24 (UTC day): no vendor-reported incident openOct 25 (UTC day): no vendor-reported incident openOct 26 (UTC day): no vendor-reported incident openOct 27 (UTC day): 0 min with a major or critical incident open, 43 min with any incident open, 1 incident startedOct 28 (UTC day): 0 min with a major or critical incident open, 2 h 23 min with any incident open, 1 incident startedOct 29 (UTC day): no vendor-reported incident openOct 30 (UTC day): 0 min with a major or critical incident open, 17 min with any incident open, 1 incident startedOct 31 (UTC day): no vendor-reported incident openNov 1 (UTC day): no vendor-reported incident openNov 2 (UTC day): no vendor-reported incident openNov 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 | 99.96% | 98.92% | 14 min | 7 h 44 min | 6 |
| Last 90 days | 99.65% | 99.25% | 7 h 29 min | 16 h 9 min | 12 |
This is what Semgrep 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: Semgrep status history · last 90 days · Semgrep status page (opens in new tab) · Markdown