Rippling outage, August 2026: Delayed sync in integrations
Rippling reported and resolved an incident: Delayed sync in integrations. It lasted 2.3 hours.
OKResolved
From Rippling's official status page, in their words.
What happened
- Started
- Resolved
- Duration
- 2.3 hours
- Impact
- major
- Affected
- Third-party integrations
- Investigating
- Identified
- Monitoring
- Resolved
Why it happened
Rippling has not given a cause in its updates. We never guess one.
How it was 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
Timeline
Oldest first, from the first notice to the resolution. From Rippling's official status page, in their words.
- 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.
- 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.
- 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.
- 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
What this means for a business (and what to check now)
- Retry anything that failed during the 2.3 hours.
- Enter any payments, bookings or jobs you took another way.
- If a deadline fell inside the window, keep this page as your record of the outage.
The full guide: what to do when a service you rely on is down
Other Rippling incidents
- Issues editing Supergroups, resolved after 1.4 hours
- QuickBooks data import delayed for some customers, resolved after 10.9 hours
- Rippling AI is down, resolved after 11 minutes
- Products partially degraded, resolved after 1.8 hours
- Issues using 1Password passkeys, resolved after 25.9 hours
Hear about the next Rippling incident as it starts
Free email alerts when the official status changes, with what to do while it is down.