Semgrep: Custom SSO Login Issues

Impact: majorStatus: resolvedStarted 2026-07-16 09:38 UTCResolved 2026-07-16 12:46 UTC (3.1 h)2 updatesSource: stspg.io

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 archived incident (Sol). Check the timeline before relying on it.

Affected components: Login/SSOsemgrep.dev - Login/SSO

Timeline of updates

investigating2026-07-16 09:38 UTC
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
resolved2026-07-16 12:46 UTC
This incident has been resolved by the third party vendor

Rewindex changes for this incident

Major incident: Custom SSO Login Issues 2026-07-16 09:38 UTC

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Semgrep profile · Recent Semgrep incidents · Markdown · JSON