Skip to main content
Rippling

Asynchronous job queue resulting in stale services

Degraded Lasted 2h 55m · started · Rippling's page

Level
confirmed
Worst impact
Degraded
Components
Rippling App
Down Index
21of 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 2h 55m it lasted.

    Anything that failed between 2026-07-28 02:23 UTC and 2026-07-28 05:17 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 2

  1. monitoring

    To mitigate a previous incident, non-critical asynchronous tasks were paused on Monday, July 27 at 9:30a PT and re-enabled around 3:30p PT. We are still working through the task backlog, and some things across Rippling - like group membership - will be stale until the remaining jobs catch up.

    provider

  2. 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-78ed75de19

Is Rippling still down?

No, this incident was resolved 2026-07-28 05:17 UTC. For Rippling's live state, see https://down.guide/rippling.

How long did it last?

2h 55m, from 2026-07-28 02:23 UTC to 2026-07-28 05:17 UTC, by the times Rippling posted.

What was affected?

Rippling named Rippling App.

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.