Live / Semgrep / Incident
Semgrep: Scans are degraded or delayed
Semgrep · semgrep.devMinor incidentResolved2026-10-28 21:39 UTC
Public — what happened
Summary
Semgrep reported a minor incident in which scans were running slower than normal or were delayed. The company said the problem began at 19:16 UTC on 2026-10-28. It stated that it had identified the issue and was working on a fix, and as of the latest update it had not been marked resolved.
Affected
Scans and CI/CD, Managed Scans
Timeline
- Started — 2026-10-28 19:16 UTC
- Identified — 2026-10-28 19:16 UTC
- Resolved — 2026-10-28 21:39 UTC · 2h 23m 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 45, 2026, our weekly internet health report.