- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Single Sign-on (SSO)
- Down Index
- 25of 100
What to do
Check whether you use Rippling Single Sign-on (SSO). Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 12m it lasted.
Anything that failed between 2026-05-27 14:01 UTC and 2026-05-27 14:12 UTC may need a replay.Subscribe to Rippling's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=rippling works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Rippling 3
- monitoring
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.
provider
- monitoring
Error rates down, continuing to monitor
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-6dfd94deb1
Is Rippling still down?
No, this incident was resolved 2026-05-27 14:12 UTC. For Rippling's live state, see https://down.guide/rippling.
How long did it last?
12m, from 2026-05-27 14:01 UTC to 2026-05-27 14:12 UTC, by the times Rippling posted.
What was affected?
Rippling named Single Sign-on (SSO).
What caused it?
Rippling hasn't published a root cause. If it does, it shows here.
Where does this come from?
Rippling's official status page, https://status.rippling.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.