# Semgrep in May 2026: incidents, uptime and changes

> Semgrep in May 2026: 4 incidents on its status page (2 major or critical), 99.54% free of major or critical incidents (vendor-reported). From Rewindex’s archive of Semgrep’s status, pricing and policy pages.

Canonical: https://rewindex.com/company/semgrep/2026/05
Last updated: 2026-06-01T00:00:00Z

- Incidents posted: 4 (major/critical: 2) · Maintenance: 1
- By vendor impact label: major 2, minor 2
- Uptime (vendor-reported): 99.54% free of major/critical incidents, 96.25% free of any incident; outage time 3 h 23 min, incident time 27 h 53 min
- Price changes: 0 · Pricing/legal/trust page changes: 0 · Deprecations: 0 · CVEs: 0
- Previous month: [April 2026](https://rewindex.com/company/semgrep/2026/04.md) · Next: [June 2026](https://rewindex.com/company/semgrep/2026/06.md) · [All months](https://rewindex.com/company/semgrep/reports.md) · [Semgrep](https://rewindex.com/company/semgrep.md)

_Uptime: 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._

## Major and critical incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [Scheduling delays for Semgrep Managed Scanning (SMS)](https://rewindex.com/company/semgrep/incidents/71vfjvft3q8x.md) | major | 2026-05-19 18:54 UTC | 2026-05-19 21:33 UTC | 2.6 h | resolved |
| [Logins are failing for users via GitHub auth](https://rewindex.com/company/semgrep/incidents/b3ns2rs4wkdt.md) | major | 2026-05-20 17:34 UTC | 2026-05-20 18:18 UTC | 44 min | resolved |

## All incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [Slow performance and intermittent errors in the Semgrep AppSec Platform](https://rewindex.com/company/semgrep/incidents/x4t3jhbttvp0.md) | minor | 2026-05-12 17:27 UTC | 2026-05-13 16:24 UTC | 23 h | resolved |
| [Scheduling delays for Semgrep Managed Scanning (SMS)](https://rewindex.com/company/semgrep/incidents/71vfjvft3q8x.md) | major | 2026-05-19 18:54 UTC | 2026-05-19 21:33 UTC | 2.6 h | resolved |
| [Managed Scans: full project scans being associated with HEAD instead of the default branch name](https://rewindex.com/company/semgrep/incidents/nlr2pcglhxlk.md) | minor | 2026-05-20 01:18 UTC | 2026-05-20 02:52 UTC | 1.6 h | resolved |
| [Logins are failing for users via GitHub auth](https://rewindex.com/company/semgrep/incidents/b3ns2rs4wkdt.md) | major | 2026-05-20 17:34 UTC | 2026-05-20 18:18 UTC | 44 min | resolved |

## Maintenance

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [\[Scheduled\] Database Maintenance for all tenants](https://rewindex.com/company/semgrep/incidents/g7p2bnz3vwzd.md) | maintenance | 2026-05-30 00:00 UTC | 2026-05-30 04:00 UTC | 4.0 h | resolved |

## Cite this

Semgrep posted 4 status incidents in May 2026 (2 major or critical); 0 price changes and 0 notable page changes observed.

- Canonical URL: https://rewindex.com/company/semgrep/2026/05
- Citation: Semgrep, “Semgrep in May 2026” (2026-05-01 00:00 UTC). Archived by Rewindex: https://rewindex.com/company/semgrep/2026/05 (CC BY 4.0).
- Markdown link: `[Semgrep: Semgrep in May 2026 (2026-05-01)](https://rewindex.com/company/semgrep/2026/05)`


---
Canonical: https://rewindex.com/company/semgrep/2026/05 · Markdown: https://rewindex.com/company/semgrep/2026/05.md · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T14:32:55.592Z