Live  /  Rippling  /  Incident

Rippling: Salesforce integrations disconnecting

Rippling · rippling.comMinor incidentResolved2026-11-11 00:03 UTC
Public — what happened

Summary

Rippling reported that some customers' connections to Salesforce had come unlinked, an issue it rated as minor and began investigating at 13:49 UTC on 2026-11-10. By 14:06 UTC the company said it had found the reason, attributing it to a change Salesforce made to how its login refresh tokens work. Rippling said it emailed the affected customers, who can restore the connection by reconnecting the integration. As of 14:44 UTC the incident was in monitoring status and had not been marked resolved.

Affected

Third-party integrations

As listed on Rippling’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Rippling against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Rippling: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Rippling report →

More from Rippling

Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.

The full archive is on the Rippling status & history page.

Related: Rippling status & history. SquidGrid is not affiliated with Rippling.