CompaniesSemgrepMonthly reportsMay 2026
Semgrep in May 2026: incidents, uptime and changes
4incidents posted
2labelled major or critical
99.54%free of major/critical
96.25%free of any incident
0price changes
0notable page changes
Vendor-reported outage time 3 h 23 min, incident time 27 h 53 min. 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. Last 90 days.
By vendor label: Major 2 · Minor 2
Major and critical incidents 2
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Scheduling delays for Semgrep Managed Scanning (SMS) | Major | 2.6 h | resolved | 05-19 | |
| Logins are failing for users via GitHub auth | Major | 44 min | resolved | 05-20 |
Other incidents 2
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Slow performance and intermittent errors in the Semgrep AppSec Platform | Minor | 23 h | resolved | 05-12 | |
| Managed Scans: full project scans being associated with HEAD instead of the default branch name | Minor | 1.6 h | resolved | 05-20 |
Maintenance 1
Show scheduled maintenance
Cite this
Semgrep posted 4 status incidents in May 2026 (2 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- Semgrep in May 2026
- Vendor
- Semgrep
- Date
- URL
- https://rewindex.com/company/semgrep/2026/05