Rippling change history

Rippling reported major degradation affecting the Rippling App, with higher-than-usual error rates across products starting 2026-10-15 19:07 UTC. The vendor identified the impacted subsystem and reported mitigation and full recovery at 2026-10-15 20:08 UTC; the incident was resolved at 2026-10-15 20:55 UTC, lasting 1 h 47 min.

Rippling reported a critical outage that prevented its app from loading, starting 2026-09-29 19:20 UTC and resolved at 2026-09-30 03:55 UTC (8 h 35 min). The vendor observed authentication database overload; access initially recovered with degraded performance, and the app was fully operational by 09-29 19:51 UTC while root-cause investigation continued.

Rippling reported a major outage in which the Rippling App loaded intermittently or not at all for employees and customers. It started at 2026-09-18 16:18 UTC and was resolved at 2026-09-18 23:00 UTC, lasting 6 h 41 min. A fix was implemented at 17:21 UTC; no cause was stated.

Rippling MCP was down in a critical-impact incident affecting Identity & App Management - Third-party integrations and Third-party integrations. It started at 2026-09-17 20:13 UTC and was resolved at 2026-09-17 20:47 UTC, lasting 34 min; Rippling reported implementing a fix but did not specify the cause.

Rippling reported a major outage preventing some saved payroll reports from loading when certain payroll fields were included. It started at 2026-08-31 22:37 UTC and lasted 5 h 43 min, resolving at 2026-09-01 04:20 UTC; United States access was restored before European Union access.

Rippling reported major data-sync delays affecting third-party integrations including Ramp and Box; admins could see disconnected accounts, but existing employee access was unaffected. Recorded start and resolution were both 2026-08-06 18:29 UTC (computed duration: 0 min). Rippling reverted a rollout-related change and retriggered syncs, recovering impacted integrations.

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.

Rippling reported a critical outage preventing access to its web and mobile apps, starting 2026-07-27 16:11 UTC and resolved at 2026-07-27 18:37 UTC (2 h 26 min). Rippling rolled back its latest deployment; access was restored at 16:32 UTC, and performance metrics were back to normal by 17:08 UTC.

Rippling reported a critical incident in which some users saw "Access denied" when accessing Rippling. It started and was resolved at 2026-07-16 09:00 UTC, with a computed duration of 0 min; Rippling said the issue was fully mitigated and service was fully operational again.

Parts of the Rippling App were degraded and not loading in a major-impact incident starting 2026-06-24 19:18 UTC. Site access returned to normal at 19:31 UTC; Rippling reported mitigation fixes at 20:10 UTC and resolved the incident at 2026-06-24 20:56 UTC, after 1 h 38 min.

Certain Rippling app pages, including the hiring flow and employee profiles, crashed in a major-impact incident from 2026-06-19 20:03 UTC to 2026-06-19 20:27 UTC, lasting 24 min. Rippling disabled the feature flag causing the issue and reported the app operational again at 20:07 UTC.

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.

Rippling reported a major incident degrading Single Sign-on (SSO) and related identity flows, starting at 2026-05-27 14:01 UTC and resolved at 2026-05-27 14:12 UTC (11 min). A fix was deployed, successful SSO logins were confirmed, and error rates fell.

Rippling reported a major outage in the Rippling App: some Payroll customers could not see upcoming runs. It started 2026-05-01 19:09 UTC and was resolved 2026-05-01 20:54 UTC, lasting 1 h 45 min, after a fix was implemented. Runs with an approval deadline of 5/1/2026 had that deadline moved to 5:30pmPT.

Rippling reported major degradation affecting Reports, Transformations, and AI assistant deep data answers, starting at 2026-03-24 23:18 UTC. The team identified the issue and implemented a fix; services were reported recovered at 2026-03-25 00:33 UTC, and the incident was resolved at 2026-03-25 00:42 UTC, with a computed duration of 1 h 23 min.

Rippling reported a major incident in which its agent did not automatically install after MDM enrollment, with cases observed on the morning of Jan 26. The recorded start and resolution were both 2026-01-28 00:30 UTC (computed duration: 0 min); Rippling said it found the root cause and fixed the issue, without specifying either.

Rippling reported a major Rippling App incident affecting timecard approvals and schedule loading, starting at 2026-01-15 15:50 UTC and lasting 2 h 23 min. A fix was implemented by 2026-01-15 17:09 UTC, and the incident was resolved at 2026-01-15 18:13 UTC.

Rippling reported major degraded performance in its Payroll application starting 2026-01-14 20:54 UTC, lasting 3 h 19 min until resolution at 2026-01-15 00:13 UTC. A fix was implemented and monitoring began at 01-14 23:27 UTC.

Rippling reported critical general service degradation affecting the Rippling App from 2025-12-16 18:47 UTC to 2025-12-16 22:35 UTC, lasting 3 h 48 min. A fix was implemented by 12-16 19:24 UTC, and the incident was resolved; no cause was stated.

Rippling reported a critical incident affecting use of job codes and dimensions in Time and Attendance and Payroll, starting 2025-11-24 20:13 UTC. A fix was implemented at 2025-11-24 20:25 UTC; the incident was resolved at 2025-11-25 08:25 UTC, with a reported duration of 12 h 11 min.

Rippling customers could not log in during a critical outage affecting Authentication and Identity & App Management - Authentication. The incident started at 2025-11-18 13:38 UTC and was resolved at 2025-11-18 17:30 UTC, lasting 3 h 52 min. Rippling attributed it to a third-party outage and reported implementing a fix at 14:21 UTC.

Rippling reported major degradation across multiple services in the Rippling App, starting 2025-11-16 18:36 UTC and resolved at 2025-11-16 19:38 UTC, lasting 1 h 1 min. Rippling attributed it to high load on a database critical to groups and reduced that load while scaling up database infrastructure.

Rippling reported a major notification degradation causing 2–15 minute authentication delays, starting 2025-10-27 15:23 UTC and resolved at 2025-10-27 18:38 UTC (3 h 14 min). Scheduled notifications were temporarily suspended to reduce database load; delivery recovered within the 10-second SLA, scheduled jobs resumed, and delayed scheduled notifications were being sent.