- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Third-party integrations
- Down Index
- 19of 100
What to do
Check whether you use Rippling Third-party integrations. 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 0m it lasted.
Anything that failed between 2026-08-06 18:29 UTC and 2026-08-06 18:29 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 4
- identified
Several integrations including Ramp and Box are experiencing delays in data syncing. Any changes to the integration are not syncing and admins may see accounts as disconnected. Existing employee access is not affected.
provider
- investigating
Several integrations including Ramp and Box are experiencing delays in data syncing. Any changes to the integration are not syncing and admins may see accounts as disconnected. Existing employee access is not affected.
provider
- monitoring
A fix has been deployed and we are rolling it out for all impacted integrations. Any data not yet synced will start resyncing automatically.
provider
- resolved
We identified an issue where some third-party integrations were showing disconnected / invalid-token behavior related to the rollout. The team reverted the change in production and retriggered syncs to recover affected integrations. - Impacted integrations, including Ramp and Box, have recovered - Some integrations that remain disconnected are unrelated to the this incident. In those cases, tokens were already revoked, expired, or deactivated, and customers may need to reconnect manually
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-0dcc210ae8
Is Rippling still down?
No, this incident was resolved 2026-08-06 18:29 UTC. For Rippling's live state, see https://down.guide/rippling.
How long did it last?
0m, from 2026-08-06 18:29 UTC to 2026-08-06 18:29 UTC, by the times Rippling posted.
What was affected?
Rippling named Third-party integrations.
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.