Istoricul incidentelor Rippling

1. 31 august 2026 la 22:37 UTCidentified

   Am identificat o problemă care împiedică unele rapoarte de salarizare salvate de la încărcarea atunci când anumite câmpuri de plată sunt incluse. Implementăm o fixare și vom oferi o altă actualizare după restabilirea accesului la raport.

2. 1 septembrie 2026 la 03:44 UTCidentified

   Am refăcut accesul la rapoartele de plată salvate pentru clienţii din Statele Unite. Continuăm să lucrăm pentru a restabili accesul la rapoarte pentru clienţii afectaţi din Uniunea Europeană şi vom oferi o altă actualizare după ce restaurarea va fi finalizată.

3. 1 septembrie 2026 la 04:20 UTCresolved

   Problema care afectează rapoartele de plată salvate a fost rezolvată, iar accesul la rapoarte a fost restabilit.

Traducere automată din actualizarea oficială a incidentului.

1. 21 august 2026 la 16:06 UTCresolved

   Acest lucru este acum rezolvat. Acesta a afectat unii utilizatori pentru < 15 minute.

Traducere automată din actualizarea oficială a incidentului.

1. 6 august 2026 la 16:12 UTCidentified

   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. 6 august 2026 la 16:36 UTCinvestigating

   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. 6 august 2026 la 18:03 UTCmonitoring

   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. 6 august 2026 la 18:29 UTCresolved

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

1. 4 august 2026 la 20:35 UTCinvestigating

   Investigăm acum

2. 4 august 2026 la 20:38 UTCmonitoring

   Problemele par rezolvate, continuând să monitorizeze

3. 4 august 2026 la 21:19 UTCresolved

   Services returned to normal

Traducere automată din actualizarea oficială a incidentului.

1. 28 iulie 2026 la 02:23 UTCmonitoring

   Pentru a atenua un incident anterior, sarcinile asincrone necritice au fost întrerupte luni, 27 iulie, la ora 9:30a PT şi re-instalate în jurul orei 3:30p PT. Încă lucrăm la lista de sarcini, iar unele lucruri de-a lungul Rippling - cum ar fi apartenenţa la grup - vor fi învechite până când restul locurilor de muncă vor recupera.

2. 28 iulie 2026 la 05:17 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 27 iulie 2026 la 20:10 UTCinvestigating

   Utilizatorii nu pot accesa aplicațiile web și mobile Rippling. Vom oferi o actualizare în următoarele 10 minute.

2. 27 iulie 2026 la 20:24 UTCinvestigating

   Accesul la Rippling este restaurat. Investigăm o modificare recentă care ar fi putut duce la o creștere a sarcinii de interogare și au crescut capacitatea de infraroșu pentru a gestiona încărcătura în perioada de timp.

3. 27 iulie 2026 la 22:47 UTCmonitoring

   Am întrerupt sarcinile necritice asincrone mai devreme pentru a restabili sănătatea locului. Deşi am reinstalat acele sarcini din nou, coada de lucru asincronă încă ne prinde din urmă. Ca urmare, unele lucruri de-a lungul Rippling - cum ar fi calitatea de membru al grupului - ar putea fi vechi până când locurile de muncă rămase vor ajunge din urmă în următoarele câteva ore.

4. 28 iulie 2026 la 02:09 UTCresolved

   Accesul la aplicația Rippling a fost restaurat complet.

Traducere automată din actualizarea oficială a incidentului.

1. 27 iulie 2026 la 16:11 UTCinvestigating

   Investigăm probleme în care utilizatorii nu pot accesa aplicațiile web și mobile Rippling. Vom oferi o actualizare în următoarele 10 minute.

2. 27 iulie 2026 la 16:23 UTCinvestigating

   Suntem în mijlocul de rulare înapoi ultima implementare. Performanţa rămâne degradată în timp ce rola este în mişcare. Următoarea actualizare în 10 minute.

3. 27 iulie 2026 la 16:32 UTCinvestigating

   Accesul la aplicația Rippling este restabilit. Monitorizăm sănătatea și performanța site-ului.

4. 27 iulie 2026 la 17:08 UTCinvestigating

   Incidentul este atenuat, deoarece indicatorii de performanță ai aplicațiilor au revenit la nivelurile normale.

5. 27 iulie 2026 la 18:37 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 16 iulie 2026 la 09:44 UTCresolved

   Rippling afişat "Access negat" unor utilizatori accesând Rippling. Problema a fost complet atenuată și Rippling este din nou complet operațional.

Traducere automată din actualizarea oficială a incidentului.

1. 10 iulie 2026 la 17:37 UTCinvestigating

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

2. 10 iulie 2026 la 18:54 UTCresolved

   This incident has been resolved.

1. 7 iulie 2026 la 16:51 UTCinvestigating

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

2. 7 iulie 2026 la 17:08 UTCidentified

   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. 7 iulie 2026 la 19:06 UTCresolved

   This incident has been resolved.

1. 24 iunie 2026 la 19:18 UTCinvestigating

   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. 24 iunie 2026 la 19:31 UTCinvestigating

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

3. 24 iunie 2026 la 20:10 UTCmonitoring

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

4. 24 iunie 2026 la 20:56 UTCresolved

   This incident has been resolved.

1. 22 iunie 2026 la 15:46 UTCidentified

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

2. 22 iunie 2026 la 16:24 UTCresolved

   This incident has been resolved.

1. 19 iunie 2026 la 20:03 UTCinvestigating

   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. 19 iunie 2026 la 20:07 UTCmonitoring

   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. 19 iunie 2026 la 20:27 UTCresolved

   This incident has been resolved.

1. 1 iunie 2026 la 16:43 UTCinvestigating

   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. 1 iunie 2026 la 16:50 UTCmonitoring

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

3. 1 iunie 2026 la 21:48 UTCresolved

   This incident has been resolved.

1. 28 mai 2026 la 16:16 UTCinvestigating

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

2. 28 mai 2026 la 16:46 UTCinvestigating

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

3. 28 mai 2026 la 16:47 UTCinvestigating

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

4. 28 mai 2026 la 17:04 UTCinvestigating

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

5. 28 mai 2026 la 19:52 UTCresolved

   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.

1. 27 mai 2026 la 13:54 UTCmonitoring

   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. 27 mai 2026 la 14:01 UTCmonitoring

   Error rates down, continuing to monitor

3. 27 mai 2026 la 14:32 UTCresolved

   This incident has been resolved.

1. 18 mai 2026 la 22:34 UTCinvestigating

   Users are reporting slowness while using Rippling

2. 19 mai 2026 la 00:37 UTCidentified

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

3. 19 mai 2026 la 00:40 UTCmonitoring

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

4. 19 mai 2026 la 00:59 UTCresolved

   This incident has been resolved.

1. 14 mai 2026 la 18:11 UTCidentified

   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. 14 mai 2026 la 20:58 UTCresolved

   The issue has been resolved

1. 6 mai 2026 la 05:49 UTCinvestigating

   Rippling AI is down. We are investigating the issue.

2. 6 mai 2026 la 05:54 UTCmonitoring

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

3. 6 mai 2026 la 06:09 UTCresolved

   Rippling AI access has been restored.

1. 1 mai 2026 la 19:09 UTCidentified

   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. 1 mai 2026 la 20:54 UTCmonitoring

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

3. 1 mai 2026 la 20:54 UTCresolved

   This incident has been resolved.