Changes / Rippling / Single-Sign-on down
Rippling: Major incident: Single-Sign-on down
Summary
Rippling reported a major incident degrading Single Sign-on (SSO) and related identity flows, starting at 2026-05-27 14:01 UTC and resolved at 2026-05-27 14:12 UTC (11 min). A fix was deployed, successful SSO logins were confirmed, and error rates fell.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Single-Sign-on down
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-05-27 14:01 UTC
Before: not present
After: 2026-05-27 14:12 UTC
Before: not present
After: Identity & App Management - Single Sign-on (SSO), Single Sign-on (SSO)
Before: not present
After: SSO and related identity flows were degraded in production, with the incident opened at 08:49 EDT. A fix has been deployed and the team is monitoring service health, with confirmed successful SSO logins.
Before: not present
After: Error rates down, continuing to monitor
Before: not present
After: This incident has been resolved.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Single-Sign-on down (this change) Rippling reported a major incident degrading Single Sign-on (SSO) and related identity flows, starting at 2026-05-27 14:01 UTC and resolved at 2026-05-27 14:12 UTC (11 min). A fix was deployed, successful SSO logins were confirmed, and error rates fell. | Major incident |