Rippling Outage History

Rippling's API Tokens page in the Developer app became inaccessible to users who had expired API tokens, preventing them from managing their tokens through the interface. Users with active API tokens were not affected and could continue normal operations. The issue was resolved after 2.8 hours once the root cause was identified and a fix was implemented.

Rippling AI experienced a complete service outage for 20 minutes on May 6th, 2026. The company implemented a fix and monitored the system before confirming that AI access was fully restored. This was classified as a minor incident despite the total service unavailability.

Rippling experienced a major incident where some payroll customers could not see their upcoming payroll runs in the app. The issue affected the Rippling App's payroll functionality, and approval deadlines for runs scheduled for 5/1/2026 were extended to 5:30pm PT to accommodate the disruption. The incident was resolved after 1.8 hours.

Rippling experienced a permissions error that prevented partial admins from completing the hiring flow at the documents step. The issue blocked administrators from sending documents to new hires during the onboarding process. The problem was resolved after 2.9 hours once the root cause was identified and a fix was deployed.

Rippling's Google Workspace integration features, including SSO and authentication, were unavailable for approximately 33 minutes due to the deletion of Google Workspace app metadata. During the outage, some notifications and workflow emails were incorrectly sent to personal email addresses instead of work emails since Google Workspace email lookups were unavailable. The incident was resolved with failed events like user provisioning and group syncs successfully replayed.

Rippling's Data features including Reports, Transformations, and AI assistant deep data answers experienced degradation for 1.4 hours. The team identified the root cause and implemented a fix to restore services. All affected systems were recovered and returned to normal operation.

Rippling experienced slow login page access for 3.5 hours due to high database load affecting the Rippling App. The team initially reverted a suspected root cause but had to continue investigating when that didn't fully resolve the issue. The incident was resolved by adding a database index to mitigate the performance problem.