Rippling 장애 기록

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. The issues are caused by database load.

We have scaled down async jobs that are contributing to the database load. Access to Rippling is starting to recover.

We are monitoring database health and site access while continuing to investigate the root causes.

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 are reporting slowness while using Rippling

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.

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.

Partial admins are blocked from completing the hiring flow due to a permissions error at the 'send documents' step. The root cause has been identified and a fix should be rolled out in about 1 hour.

The issue has been resolved

Google Workspace integration features, including SSO, were unavailable for a 15-30 min period of time earlier today. Access has been restored, but we are investigating to confirm no ongoing impact for customers.

The root cause of this incident was deletion of Google Workspace app metadata, which made Google Workspace integration features unavailable. The impacted timeframe was 4/16/2026 10:59 AM PDT to 11:32 AM PDT. We are continuing to investigate the services impacted during that time period.

Some Rippling Notifications and emails from Workflow Studio were sent to personal email accounts during the affected window since lookup of Google Workspace work emails were unavailable

The incident has been resolved. Events that failed during the affected window - such as user provisioning and group syncs - were successfully replayed.

Systems underlying Rippling Data features (Reports, Transformations, AI assistant deep data answers) are currently degraded. The team has identified the issue and is implementing a fix.

Services are recovered. We are continuing to monitor to ensure no further degradation.

This incident has been resolved.

Access to the Rippling app login page is slow due to high database load. We have identified the root cause and are working on a fix.

We reverted the issue that was believed to be the root cause, but it did not fully resolve the issue. We are continuing to investigate the root cause while working on mitigating the impact.

The impact has been mitigated, with app access operational again

We added a database index and have mitigated the issue

This incident has been resolved.

We are addressing an issue causing slowness across Rippling services

We have implemented a fix to scale up pods and are seeing services begin to recover. We are monitoring the impact.

This incident has been resolved.

On the morning of Jan 26, we saw cases where the Rippling agent did not automatically install after MDM enrollment. We found the root cause and fixed the issue. It is now resolved.

We are investigating issues where search functionality is timing out, resulting in errors

A fix has been implemented and search functionality is working properly

This incident has been resolved.

We are currently investigating this issue.

The incident was due to feature flags failing and routing to a prior version of the Reports application. The issue has been mitigated, and we are monitoring the behavior.

This incident has been resolved.