Live / Semgrep / Incident
Semgrep: Intermittent login failures on semgrep.dev
Semgrep · semgrep.devMajor incidentResolved2026-10-05 16:14 UTC
Public — what happened
Summary
Semgrep reported a major incident in which some people had trouble signing in to semgrep.dev, with failures happening on and off. The company said the problem hit users logging in through GitHub and GitLab, some of whom were shown an error page after pressing Continue. Semgrep posted at 16:00 UTC on October 5, 2026 that it had found the cause, though it did not say what it was, and the incident was marked resolved at 16:14.
Affected
Login/SSO
Timeline
- Started — 2026-10-05 16:00 UTC
- Identified — 2026-10-05 16:00 UTC
- Resolved — 2026-10-05 16:14 UTC · 14 min 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 42, 2026, our weekly internet health report.