- Level
- confirmed
- Worst impact
- Major outage
- Components
- Rippling App
- Down Index
- 45of 100
What to do
Check whether you use Rippling Rippling App. 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 8h 35m it lasted.
Anything that failed between 2026-09-29 19:20 UTC and 2026-09-30 03:55 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.
Root cause
We are continuing to investigate the root cause of the database overload.
Category: Capacity
Read the postmortemUpdates from Rippling 5
- investigating
We are investigating issues where the Rippling app is not loading. We will provide an update within the next 10 minutes.
provider
- investigating
We observed an overload in utilization of our authentication database. Access to Rippling has started to recover but there may be some degraded performance.
provider
- investigating
The Rippling app is fully operational again. We are continuing to investigate the root cause of the database overload.
provider
- monitoring
The Rippling app is fully operational again. We are continuing to investigate the root cause of the database overload.
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-16bbbc97e0
Is Rippling still down?
No, this incident was resolved 2026-09-30 03:55 UTC. For Rippling's live state, see https://down.guide/rippling.
How long did it last?
8h 35m, from 2026-09-29 19:20 UTC to 2026-09-30 03:55 UTC, by the times Rippling posted.
What was affected?
Rippling named Rippling App.
What caused it?
Capacity. Rippling wrote: "We are continuing to investigate the root cause of the database overload." The postmortem: https://stspg.io/jlwnt47313kk
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.