Live / Semgrep / Incident
Semgrep: Possibly Delayed Scans
Semgrep · semgrep.devMinor incidentResolved2026-11-07 00:53 UTC
Public — what happened
Summary
Semgrep reported an incident titled "Possibly Delayed Scans," which it rated minor, beginning at 23:46 UTC on 2026-11-06. The company said it was seeing an AWS EC2 failure in at least one region, but that it had enough capacity to handle its current load. At 00:09 UTC on 2026-11-07 Semgrep said it was starting to see recovery and would keep monitoring, and it marked the incident resolved at 00:53 UTC.
Affected
AWS ec2-us-west-2, Managed Scans
Timeline
- Started — 2026-11-06 23:46 UTC
- Identified — 2026-11-06 23:46 UTC
- Monitoring — 2026-11-07 00:09 UTC
- Resolved — 2026-11-07 00:53 UTC · 1h 07m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Semgrep against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Semgrep: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Semgrep report →
More from Semgrep
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.