Changes / Rippling / Rippling app outage
Rippling: Major incident: Rippling app outage
Summary
Rippling reported a major app and SSO outage from 2026-05-28 16:16 UTC to 2026-05-28 19:52 UTC, lasting 3 h 35 min. Database load caused the issues; Rippling scaled down contributing async jobs before re-enabling them. Supergroup membership latency delayed some access changes; Rippling reported all access and functionality restored and group memberships refreshed.
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 outage
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-05-28 16:16 UTC
Before: not present
After: 2026-05-28 19:52 UTC
Before: not present
After: Identity & App Management - Single Sign-on (SSO), Rippling App, Single Sign-on (SSO)
Before: not present
After: We are investigating issues with the Rippling app and SSO. The issues are caused by database load.
Before: not present
After: We have scaled down async jobs that are contributing to the database load. Access to Rippling is starting to recover.
Before: not present
After: We are monitoring database health and site access while continuing to investigate the root causes.
Before: not present
After: We are starting to re-enable the async jobs that have been throttled while monitoring the database load.
Before: not present
After: All access and functionality to Rippling should be back to normal. Supergroup membership had high latency during the incident period, resulting in some delays to access changes, but all group memberships have been refreshed and will update normally moving forward.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Rippling app outage (this change) Rippling reported a major app and SSO outage from 2026-05-28 16:16 UTC to 2026-05-28 19:52 UTC, lasting 3 h 35 min. Database load caused the issues; Rippling scaled down contributing async jobs before re-enabling them. Supergroup membership latency delayed some access changes; Rippling reported all access and functionality restored and group memberships refreshed. | Major incident |