- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Third-party integrations
- Down Index
- 34of 100
Summary
Rippling says some customer Salesforce integrations are disconnected due to a change in refresh token lifecycle by Salesforce. Impacted customers have been emailed and can reconnect the integration to restore it; the incident is currently in monitoring.
Written by anthropic/claude-haiku-5.5 from Rippling's own updates.
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 10h 14m it lasted.
Anything that failed between 2026-11-10 13:49 UTC and 2026-11-11 00:03 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 5
- investigating
We are currently investigating this issue.
provider
- identified
Some customer integrations with Salesforce are disconnected due to a change in refresh token lifecycle by Salesforce
provider
- identified
Some customer integrations with Salesforce are disconnected due to a change in refresh token lifecycle by Salesforce. Email notifications have been sent to impacted customers. Impacted customers can reconnect the integration to restore it.
provider
- monitoring
Some customer integrations with Salesforce are disconnected due to a change in refresh token lifecycle by Salesforce. Email notifications have been sent to impacted customers. Impacted customers can reconnect the integration to restore it.
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-542562b2a7
Is Rippling still down?
No, this incident was resolved 2026-11-11 00:03 UTC. For Rippling's live state, see https://down.guide/providers/rippling.
How long did it last?
10h 14m, from 2026-11-10 13:49 UTC to 2026-11-11 00:03 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.