Rippling had 47 outages in the last 2 years totaling 74h 58m of downtime — averaging 1.9 incidents per month.
There were 47 Rippling outages since September 11, 2025 totaling 74h 58m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are experiencing higher than usual error rates across our products. We've identified the impacted subsystem and mitigation is in progress.
We mitigated the issue and are fully recovered.
This incident has been resolved.
Users with version 8.12.40.31 of the 1Password Chrome extension may be unable to complete passkey verification to sign in, or add new Rippling passkeys to their account. 1Password is preparing a fix, and we will share another update when more information is available.
Rippling passkey sign-in and creation are restored with 1Password extension version 8.12.41, now available for Chrome, Edge, and Safari. Updating the extension restores Rippling passkey functionality; Firefox users were not affected.
This incident has been resolved.
On October 6, some users were unable to sign in to the RPass Chrome extension. We reverted the change that caused the issue and confirmed sign-in was restored by 3:00 PM PDT.
We are investigating issues where the Rippling app is not loading. We will provide an update within the next 10 minutes.
We observed an overload in utilization of our authentication database. Access to Rippling has started to recover but there may be some degraded performance.
The Rippling app is fully operational again. We are continuing to investigate the root cause of the database overload.
The Rippling app is fully operational again. We are continuing to investigate the root cause of the database overload.
This incident has been resolved.
Rippling is loading intermittently/not at all for both employees and customers
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing a technical outage, impacting our live chat and support email systems. We'll provide an update in 30 minutes or sooner if additional information becomes available.
The system outage affecting live chat and support emails remains ongoing. We are continuing to monitor the situation and will provide another update in 30 minutes or sooner if additional information becomes available.
The technical outage impacting our live chat and email support has been fully resolved. All support channels are operating normally, and our team is actively responding to all pending inquiries.
Latency of APIs, Functions, and App Studio page loads increased due to a migration that overloaded the database.
We have identified an issue preventing some saved payroll reports from loading when certain payroll fields are included. We are implementing a fix and will provide another update once report access has been restored.
We have restored access to affected saved payroll reports for customers in the United States. We are continuing work to restore report access for affected customers in the European Union and will provide another update once restoration is complete.
The issue affecting saved payroll reports has been resolved, and report access has been restored.
This is now resolved. It affected some users for <15 minutes.
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.
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.
A fix has been deployed and we are rolling it out for all impacted integrations. Any data not yet synced will start resyncing automatically.
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
We are currently investigating
Issues seem resolved, continuing to monitor
Services returned to normal
To mitigate a previous incident, non-critical asynchronous tasks were paused on Monday, July 27 at 9:30a PT and re-enabled around 3:30p PT. We are still working through the task backlog, and some things across Rippling - like group membership - will be stale until the remaining jobs catch up.
This incident has been resolved.
Rippling displayed "Access denied" to some users accessing Rippling. The issue has been fully mitigated and the Rippling is fully operational again.
Some AI capabilities, including building or editing AI dashboards, are unavailable.
This incident has been resolved.
We are investigating degraded performance of the Rippling app loading. We will share an update in the next 10 minutes.
We have identified the task that was overloading the system and have mitigated the issue. There were timeouts occurring for ~10 minutes but the site is operational again.
This incident has been resolved.
We are aware of issues with the Rippling app loading. Some parts of the Rippling app are degraded and not loading. We are investigating.
Access to the site is back to normal, but we are continuing to investigate and address the root cause.
We've made fixes to mitigate the issue and are monitoring the results.
This incident has been resolved.
Rippling AI actions are currently not working. The issue has been identified and a fix is being deployed.
This incident has been resolved.
We are investigating issues where certain pages in the Rippling app, like the hiring flow and employee profile pages, are crashing. We are working to mitigate the issues and investigate the root cause.
We discovered the root cause and have turned off a feature flag that was causing the issue. The issue is mitigated, and the Rippling app is operational again.
This incident has been resolved.
Some customers are experiencing issues with the side navigation loading in app.rippling.com. Apps are still accessible from the search bar. We are rolling back to a previous version of the app while we investigate the root cause. We'll share an update in the next 10 minutes.
The rollback was successful, and we are seeing the navigation bar load normally. We are monitoring the results.
This incident has been resolved.
We are investigating issues with the Rippling app and SSO
Access to Rippling is starting to recover
We are continuing to investigate this issue.
We are starting to re-enable the async jobs that have been throttled while monitoring the database load.
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.
SSO and related identity flows were degraded in production, with the incident opened at 08:49 EDT. A fix has been deployed and the team is monitoring service health, with confirmed successful SSO logins.
Error rates down, continuing to monitor
This incident has been resolved.
Users with an expired API token are unable to access Rippling’s API Tokens page in the Developer app. Active API tokens are not impacted. The root cause has been identified, and we are implementing a fix.
The issue has been resolved
Rippling AI is down. We are investigating the issue.
A fix has been implemented and we are monitoring the results.
Rippling AI access has been restored.
Some customers on Payroll are not seeing upcoming runs. For runs with an approval deadline of 5/1/2026, the approval deadline has been moved to 5:30pmPT.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.