Changes / Semgrep / Login and scans are failing for some users

Semgrep: Major incident: Login and scans are failing for some users

Summary

Semgrep reported a major outage affecting some users’ logins, managed scan starts, and CI scan result processing from 2026-04-20 20:37 UTC to 2026-04-21 00:29 UTC, lasting 3 h 51 min. Semgrep identified backend issues without detailing the cause; scans and logins were processing normally at resolution.

Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.

Major incidentLabel: outage (model (Jev), 100%)Changed Detected Source: stspg.io (opens in new tab)

What changed

AddedTitle#1
Before: not present
After: Login and scans are failing for some users
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-04-20 20:37 UTC
AddedResolved time#5
Before: not present
After: 2026-04-21 00:29 UTC
AddedAffected components#6
Before: not present
After: Login/SSO, Managed Scans, semgrep.dev - Login/SSO, semgrep.dev - Managed Scans
AddedUpdateinvestigating#7
Before: not present
After: Some users are unable to log in; some managed scans are failing to start, and CI scans may not be able to process results. We're investigating the cause of all three.
AddedUpdateidentified#8
Before: not present
After: We've identified the cause of the backend issues. Some traffic has resumed but services are still degraded, and we're continuing to remediate.
AddedUpdateresolved#9
Before: not present
After: The problem is resolved and scans and logins are now processing normally.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Major incident: Login and scans are failing for some users (this change)
Semgrep reported a major outage affecting some users’ logins, managed scan starts, and CI scan result processing from 2026-04-20 20:37 UTC to 2026-04-21 00:29 UTC, lasting 3 h 51 min. Semgrep identified backend issues without detailing the cause; scans and logins were processing normally at resolution.
Major incident

All Semgrep changes → · Semgrep profile · Markdown · JSON