Rippling

Affected: Rippling App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-15 19:07 UTC

   We are experiencing higher than usual error rates across our products. We've identified the impacted subsystem and mitigation is in progress.

2. monitoring 2026-10-15 20:08 UTC

   We mitigated the issue and are fully recovered.

3. resolved 2026-10-15 20:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-10-07 20:07 UTC

   Users with version 8.12.40.31 of the 1Password browser 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.

2. monitoring 2026-10-08 18:50 UTC

   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.

3. resolved 2026-10-08 21:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-06 18:00 UTC

   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.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-29 19:20 UTC

   We are investigating issues where the Rippling app is not loading. We will provide an update within the next 10 minutes.

2. investigating 2026-09-29 19:28 UTC

   We observed an overload in utilization of our authentication database. Access to Rippling has started to recover but there may be some degraded performance.

3. investigating 2026-09-29 19:51 UTC

   The Rippling app is fully operational again. We are continuing to investigate the root cause of the database overload.

4. monitoring 2026-09-29 19:52 UTC

   The Rippling app is fully operational again. We are continuing to investigate the root cause of the database overload.

5. resolved 2026-09-30 03:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-18 16:18 UTC

   Rippling is loading intermittently/not at all for both employees and customers

2. investigating 2026-09-18 16:19 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-09-18 17:21 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-09-18 23:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Third-party integrations

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-17 20:13 UTC

   We are currently investigating this issue.

2. identified 2026-09-17 20:20 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-09-17 20:27 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-09-17 20:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-09-16 11:22 UTC

   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.

2. identified 2026-09-16 12:21 UTC

   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.

3. resolved 2026-09-16 13:34 UTC

   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.

Excerpts are shortened. Read the full incident on Rippling's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-09-10 16:30 UTC

   Rippling REST APIs experienced increased latency beginning September 10th, 2026 11:21 AM EST. The issue was resolved September 10th, 2026 2:20 PM EST. During this window, Functions and App Studio pages that rely on REST APIs may have resulted in failures due to timeout...

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Reports & Dashboards

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-08-31 22:37 UTC

   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.

2. identified 2026-09-01 03:44 UTC

   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.

3. resolved 2026-09-01 04:20 UTC

   The issue affecting saved payroll reports has been resolved, and report access has been restored.

Excerpts are shortened. Read the full incident on Rippling's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-08-21 16:06 UTC

   This is now resolved. It affected some users for <15 minutes.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Third-party integrations

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-06 16:12 UTC

   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.

2. investigating 2026-08-06 16:36 UTC

   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.

3. monitoring 2026-08-06 18:03 UTC

   A fix has been deployed and we are rolling it out for all impacted integrations. Any data not yet synced will start resyncing automatically.

4. resolved 2026-08-06 18:29 UTC

   We identified an issue where some third-party integrations were showing disconnected / invalid-token behavior related to the rollout. The team reverted the change in production and retriggered syncs to recover affected integrations. - Impacted integrations, including Ramp and...

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App, Single Sign-on (SSO), Payroll

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-04 20:35 UTC

   We are currently investigating

2. monitoring 2026-08-04 20:38 UTC

   Issues seem resolved, continuing to monitor

3. resolved 2026-08-04 21:19 UTC

   Services returned to normal

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-07-28 02:23 UTC

   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...

2. resolved 2026-07-28 05:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A configuration change. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-27 20:10 UTC

   Users are unable to access the Rippling web and mobile apps. We will provide an update within the next 10 minutes.

2. investigating 2026-07-27 20:24 UTC

   Access to Rippling is restored. We are investigating a recent change that may have resulted in an increase in query load and have increased infra capacity to handle the load in the interim.

3. monitoring 2026-07-27 22:47 UTC

   We paused non-critical asynchronous tasks earlier today to restore site health. Although we have re-enabled those tasks again, the asynchronous task queue is still catching up. As a result, some things across Rippling - like group membership - could be stale until the remaining...

4. resolved 2026-07-28 02:09 UTC

   Access to the Rippling app has been fully restored.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-27 16:11 UTC

   We are investigating issues where users are unable to access the Rippling web and mobile apps. We will provide an update within the next 10 minutes.

2. investigating 2026-07-27 16:23 UTC

   We are in the middle of rolling back the latest deployment. Performance remains degraded while the rollback is in motion. Next update within 10 minutes.

3. investigating 2026-07-27 16:32 UTC

   Access to the Rippling app is restored. We are monitoring site health and performance.

4. investigating 2026-07-27 17:08 UTC

   The incident is mitigated, as app performance metrics are back to normal levels.

5. resolved 2026-07-27 18:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-07-16 09:00 UTC

   Rippling displayed "Access denied" to some users accessing Rippling. The issue has been fully mitigated and Rippling is fully operational again.

Excerpts are shortened. Read the full incident on Rippling's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-10 17:37 UTC

   Some AI capabilities, including building or editing AI dashboards, are unavailable.

2. resolved 2026-07-10 18:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-07 16:51 UTC

   We are investigating degraded performance of the Rippling app loading. We will share an update in the next 10 minutes.

2. identified 2026-07-07 17:08 UTC

   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.

3. resolved 2026-07-07 19:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-24 19:18 UTC

   We are aware of issues with the Rippling app loading. Some parts of the Rippling app are degraded and not loading. We are investigating.

2. investigating 2026-06-24 19:31 UTC

   Access to the site is back to normal, but we are continuing to investigate and address the root cause.

3. monitoring 2026-06-24 20:10 UTC

   We've made fixes to mitigate the issue and are monitoring the results.

4. resolved 2026-06-24 20:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Platform API

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-22 15:46 UTC

   Rippling AI actions are currently not working. The issue has been identified and a fix is being deployed.

2. resolved 2026-06-22 16:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-19 20:03 UTC

   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.

2. monitoring 2026-06-19 20:07 UTC

   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.

3. resolved 2026-06-19 20:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-01 16:43 UTC

   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.

2. monitoring 2026-06-01 16:50 UTC

   The rollback was successful, and we are seeing the navigation bar load normally. We are monitoring the results.

3. resolved 2026-06-01 21:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App, Single Sign-on (SSO)

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-28 16:16 UTC

   We are investigating issues with the Rippling app and SSO. The issues are caused by database load.

2. investigating 2026-05-28 16:46 UTC

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

3. investigating 2026-05-28 16:48 UTC

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

4. investigating 2026-05-28 17:04 UTC

   We are starting to re-enable the async jobs that have been throttled while monitoring the database load.

5. resolved 2026-05-28 19:52 UTC

   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.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Single Sign-on (SSO)

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-05-27 13:54 UTC

   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.

2. monitoring 2026-05-27 14:01 UTC

   Error rates down, continuing to monitor

3. resolved 2026-05-27 14:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-18 22:34 UTC

   Users are reporting slowness while using Rippling

2. identified 2026-05-19 00:37 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-05-19 00:40 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-05-19 00:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-05-14 18:11 UTC

   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.

2. resolved 2026-05-14 20:58 UTC

   The issue has been resolved

Excerpts are shortened. Read the full incident on Rippling's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-06 05:49 UTC

   Rippling AI is down. We are investigating the issue.

2. monitoring 2026-05-06 05:54 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-05-06 06:09 UTC

   Rippling AI access has been restored.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-05-01 19:09 UTC

   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.

2. monitoring 2026-05-01 20:54 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-05-01 20:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-04-21 18:01 UTC

   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.

2. resolved 2026-04-21 20:48 UTC

   The issue has been resolved

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Single Sign-on (SSO), Workflow Studio, Authentication, Notifications, Third-party integrations

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-04-16 18:52 UTC

   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.

2. identified 2026-04-16 19:36 UTC

   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...

3. identified 2026-04-16 19:46 UTC

   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

4. resolved 2026-04-16 23:02 UTC

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

Excerpts are shortened. Read the full incident on Rippling's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-03-24 23:18 UTC

   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.

2. monitoring 2026-03-25 00:33 UTC

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

3. resolved 2026-03-25 00:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-03-08 14:41 UTC

   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.

2. investigating 2026-03-08 15:00 UTC

   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.

3. investigating 2026-03-08 15:09 UTC

   The impact has been mitigated, with app access operational again

4. monitoring 2026-03-08 15:20 UTC

   We added a database index and have mitigated the issue

5. resolved 2026-03-08 18:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-02-02 14:52 UTC

   We are addressing an issue causing slowness across Rippling services

2. monitoring 2026-02-02 15:14 UTC

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

3. resolved 2026-02-02 15:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-01-28 00:30 UTC

   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.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-20 17:07 UTC

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

2. monitoring 2026-01-20 17:29 UTC

   A fix has been implemented and search functionality is working properly

3. resolved 2026-01-20 17:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-19 17:34 UTC

   We are currently investigating this issue.

2. monitoring 2026-01-19 18:59 UTC

   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.

3. resolved 2026-01-20 05:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-15 15:50 UTC

   We are currently investigating this issue.

2. investigating 2026-01-15 15:50 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-01-15 17:09 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-01-15 18:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-14 20:54 UTC

   We are currently experiencing degraded performance in our Payroll application. We are investigating this issue.

2. monitoring 2026-01-14 23:27 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-01-15 00:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-16 18:47 UTC

   We are currently investigating this issue.

2. monitoring 2025-12-16 19:24 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-12-16 22:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-01 17:57 UTC

   We are investigating issues accessing the Rippling app

2. monitoring 2025-12-01 18:16 UTC

   The Rippling app is operational again. We are monitoring health.

3. resolved 2025-12-01 19:30 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Rippling's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-24 20:13 UTC

   We are currently investigating this issue.

2. identified 2025-11-24 20:15 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-11-24 20:25 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-11-25 08:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-21 19:53 UTC

   We are investigating issues that are preventing users from loading the Time & Attendance app

2. investigating 2025-11-21 20:06 UTC

   Access to Time & Attendance has recovered. We are continuing to investigate to address the root cause.

3. monitoring 2025-11-22 03:52 UTC

   We have identified the root causes and continue to monitor the health

4. resolved 2025-11-24 01:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Authentication

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-11-18 13:38 UTC

   Rippling customers are unable to login due to a 3rd-party outage

2. identified 2025-11-18 14:05 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-11-18 14:21 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-11-18 17:30 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-11-16 18:36 UTC

   We are experiencing degradation across multiple services due to high load on a database critical to groups

2. monitoring 2025-11-16 18:45 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-11-16 19:38 UTC

   Our team has made changes to reduce load on the groups database and has scaled up the database infrastructure to accommodate additional load. The incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-11-05 19:04 UTC

   We are aware of an issue where users are unable to access the Payroll app. The root cause has been identified and will be resolved within the next hour.

2. resolved 2025-11-05 20:02 UTC

   Issue is now resolved. We have automatically extended the approval deadline for runs that had an approval date of November 5th. US-funded pay runs now have an approval time of 5pm PT, and Canada-funded runs have an approval deadline of 4pm PT.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Devices app

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-29 21:34 UTC

   There is a disruption to our device trust product on Chrome 142. Engineering is investigating.

2. identified 2025-10-30 15:48 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2025-10-30 18:16 UTC

   Chrome version 142 prompts users to allow sites to make local network calls. This impacts Device Trust, which relies on a local network call to allow trusted devices to access these sites. We are working on a fix to this issue, which will be deployed between Friday Oct 31 and...

4. monitoring 2025-11-04 07:49 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2025-11-06 19:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App, Notifications

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-27 15:23 UTC

   Customers may be experiencing a delay in notifications causing authentication delays. We are observing a 2 - 15 minute delay in notifications. This is under investigation.

2. investigating 2025-10-27 16:17 UTC

   We are temporarily suspending scheduled notification jobs in order to bring down the database load so that all other notifications -- including time-sensitive authentication notifications -- can recover to be delivered within SLA.

3. investigating 2025-10-27 17:02 UTC

   We have partial recovery where new notifications are being sent within the SLA of 10 seconds. Scheduled notifications continue to be suspended.

4. monitoring 2025-10-27 18:24 UTC

   The notification service has been restored, and notifications are now properly getting sent within the SLA. Scheduled notification jobs have been restored, so moving forward they will be sent at the scheduled time. Scheduled notifications that were scheduled to be sent during...

5. resolved 2025-10-27 18:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App, Notifications

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-10-01 18:11 UTC

   Email notification deliverability was disrupted from 5:29 AM PDT to 8:52 AM PDT, resulting in email notifications not getting sent during that time period. Email notifications are now getting delivered properly, but our engineering team is working to re-send the notifications...

2. identified 2025-10-01 18:18 UTC

   We are continuing to work on a fix for this issue.

3. monitoring 2025-10-01 20:25 UTC

   We have re-initiated sending the notifications that failed to send during the outage. We are monitoring those notifications getting sent successfully.

4. resolved 2025-10-01 21:33 UTC

   The incident has been resolved; notifications that failed to send during the outage period (5:29 AM - 8:52 AM PDT) were re-sent between 12:40 PM - 1:30 PM PDT.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Rippling App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-09-24 12:45 UTC

   The issue has been identified and a fix is being implemented.

2. monitoring 2025-09-24 13:46 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-09-25 06:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.

Affected: Devices app

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-09-16 20:09 UTC

   Our engineering team has identified an issue with Mac devices upgrading to macOS 26 (Tahoe) despite having a policy in place to defer major upgrades. This has occurred for companies with an OS update policy that has both deferral and major upgrade enforcement settings in place....

2. monitoring 2025-09-17 00:30 UTC

   A fix has been implemented going forward, and we are monitoring the results. We are also running a migration in batches to ensure affected devices have the correct OS update settings on the device.

3. resolved 2025-09-19 21:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rippling's status page.