Changes / Rippling / Rippling app is down
Rippling: Critical incident: Rippling app is down
Summary
Rippling’s critical outage blocked web and mobile app access starting 2026-07-27 20:10 UTC and was resolved after 5 h 58 min. Access returned earlier, but queued tasks could leave group membership stale. Rippling increased infrastructure capacity and paused non-critical asynchronous tasks while investigating a recent change that may have increased query load.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Rippling app is down
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2026-07-27 20:10 UTC
Before: not present
After: 2026-07-28 02:09 UTC
Before: not present
After: Rippling App
Before: not present
After: Users are unable to access the Rippling web and mobile apps. We will provide an update within the next 10 minutes.
Before: not present
After: Access to Rippling is restored. We are investigating a recent change that may have resulted in an increase in query load and have increased infra capacity to handle the load in the interim.
Before: not present
After: We paused non-critical asynchronous tasks earlier today to restore site health. Although we have re-enabled those tasks again, the asynchronous task queue is still catching up. As a result, some things across Rippling - like group membership - could be stale until the remaining jobs catch up over the next few hours.
Before: not present
After: Access to the Rippling app has been fully restored.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Rippling app is down (this change) Rippling’s critical outage blocked web and mobile app access starting 2026-07-27 20:10 UTC and was resolved after 5 h 58 min. Access returned earlier, but queued tasks could leave group membership stale. Rippling increased infrastructure capacity and paused non-critical asynchronous tasks while investigating a recent change that may have increased query load. | Major incident |