Changes / Semgrep / Custom SSO Login Issues

Semgrep: Major incident: Custom SSO Login Issues

Summary

Customers with custom SSO configurations could not log in to Semgrep and saw 504 Gateway Timeout errors. The major-impact incident started at 2026-07-16 09:38 UTC and was resolved at 2026-07-16 12:46 UTC, lasting 3 h 7 min. Semgrep stated that the third-party vendor resolved it.

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

What changed

AddedTitle#1
Before: not present
After: Custom SSO Login Issues
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-07-16 09:38 UTC
AddedResolved time#5
Before: not present
After: 2026-07-16 12:46 UTC
AddedAffected components#6
Before: not present
After: Login/SSO, semgrep.dev - Login/SSO
AddedUpdateinvestigating#7
Before: not present
After: We're aware of an issue where customers with custom SSO configs are unable to login to Semgrep and are seeing a 504 Gateway Timeout error. The issue is under investigation
AddedUpdateresolved#8
Before: not present
After: This incident has been resolved by the third party vendor

First version of this incident archived by Rewindex. View the live incident.

History of this incident

When (UTC)ChangeKind
Major incident: Custom SSO Login Issues (this change)
Customers with custom SSO configurations could not log in to Semgrep and saw 504 Gateway Timeout errors. The major-impact incident started at 2026-07-16 09:38 UTC and was resolved at 2026-07-16 12:46 UTC, lasting 3 h 7 min. Semgrep stated that the third-party vendor resolved it.
Major incident

All Semgrep changes → · Semgrep profile · Markdown · JSON