Rippling incident

Delayed sync in integrations

Major Resolved View vendor source →

Rippling experienced a major incident on August 6, 2026 affecting Third-party integrations, lasting —. The incident has been resolved; the full update timeline is below.

Started
Aug 06, 2026, 06:29 PM UTC
Resolved
Aug 06, 2026, 06:29 PM UTC
Duration
—
Detected by Pingoru
Aug 06, 2026, 06:29 PM UTC

Affected components

Third-party integrations

Update timeline

  1. identified Aug 06, 2026, 04:12 PM UTC

    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.

  2. investigating Aug 06, 2026, 04:36 PM UTC

    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.

  3. monitoring Aug 06, 2026, 06:03 PM UTC

    A fix has been deployed and we are rolling it out for all impacted integrations. Any data not yet synced will start resyncing automatically.

  4. resolved Aug 06, 2026, 06:29 PM UTC

    We identified an issue where some third-party integrations were showing disconnected / invalid-token behavior related to the FluxProxy 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