- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 28of 100
What to do
Check whether your product depends on Rippling. 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 1h 24m it lasted.
Anything that failed between 2026-03-24 23:18 UTC and 2026-03-25 00:42 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
- identified
Systems underlying Rippling Data features (Reports, Transformations, AI assistant deep data answers) are currently degraded. The team has identified the issue and is implementing a fix.
provider
- monitoring
Services are recovered. We are continuing to monitor to ensure no further degradation.
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-0d453c921b
Is Rippling still down?
No, this incident was resolved 2026-03-25 00:42 UTC. For Rippling's live state, see https://down.guide/rippling.
How long did it last?
1h 24m, from 2026-03-24 23:18 UTC to 2026-03-25 00:42 UTC, by the times Rippling posted.
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.