- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Rippling AI
- Down Index
- 25of 100
What to do
Check whether you use Rippling Rippling AI. 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 11m it lasted.
Anything that failed between 2026-10-28 06:44 UTC and 2026-10-28 06: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 identified the root cause and are remediating the problem.Read the postmortem
Updates from Rippling 3
- identified
Rippling AI is not responding to user queries. We identified the root cause and are remediating the problem.
provider
- monitoring
We deployed a fix and the system has started to recover. Full recovery is rolling out.
provider
- resolved
Rippling AI is fully recovered.
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-f259501937
Is Rippling still down?
No, this incident was resolved 2026-10-28 06:55 UTC. For Rippling's live state, see https://down.guide/rippling.
How long did it last?
11m, from 2026-10-28 06:44 UTC to 2026-10-28 06:55 UTC, by the times Rippling posted.
What was affected?
Rippling named Rippling AI.
What caused it?
Rippling wrote: "We identified the root cause and are remediating the problem." The postmortem: https://stspg.io/cylx4fvpll3k
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.