Histórico de interrupções do Rippling

1. 31 Eost 2026 da 22:37 UTCidentified

   Nós identificamos um problema impedindo alguns relatórios de folha de pagamento salvos de carregar quando certos campos de folha de pagamento estão incluídos. Estamos implementando uma correção e forneceremos outra atualização quando o acesso ao relatório tiver sido restaurado.

2. 1 Gwengolo 2026 da 03:44 UTCidentified

   Nós restauramos o acesso aos relatórios de folha de pagamento salvos afetados para clientes nos Estados Unidos. Continuamos a trabalhar no sentido de restabelecer o acesso aos relatórios dos clientes afectados na União Europeia e forneceremos outra actualização quando a restauração estiver concluída.

3. 1 Gwengolo 2026 da 04:20 UTCresolved

   O problema que afeta os relatórios de folha de pagamento salvos foi resolvido e o acesso ao relatório foi restaurado.

Traduzido automaticamente da atualização oficial do incidente.

1. 21 Eost 2026 da 16:06 UTCresolved

   Isto está agora resolvido. Afetou alguns usuários por <15 minutos.

Traduzido automaticamente da atualização oficial do incidente.

1. 6 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 20:35 UTCinvestigating

   We are currently investigating

2. 4 Eost 2026 da 20:38 UTCmonitoring

   Issues seem resolved, continuing to monitor

3. 4 Eost 2026 da 21:19 UTCresolved

   Services returned to normal

Traduzido automaticamente da atualização oficial do incidente.

1. 28 Gouere 2026 da 02:23 UTCmonitoring

   Para mitigar um incidente anterior, as tarefas assíncronas não-críticas foram pausadas na segunda-feira, 27 de julho às 9:30a PT e reabilitadas por volta das 3:30p PT. Ainda estamos a trabalhar no atraso das tarefas, e algumas coisas em Rippling - como a adesão a um grupo - vão ficar paralisadas até que os restantes empregos se recuperem.

2. 28 Gouere 2026 da 05:17 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 27 Gouere 2026 da 20:10 UTCinvestigating

   Os usuários são incapazes de acessar o Rippling web e aplicativos móveis. Forneceremos uma atualização nos próximos 10 minutos.

2. 27 Gouere 2026 da 20:24 UTCinvestigating

   O acesso ao Rippling é restaurado. Estamos investigando uma mudança recente que pode ter resultado em um aumento na carga de consulta e ter aumentado a capacidade infra infra para lidar com a carga no ínterim.

3. 27 Gouere 2026 da 22:47 UTCmonitoring

   Pausamos tarefas assíncronas não críticas hoje cedo para restaurar a saúde do local. Embora tenhamos novamente habilitado essas tarefas, a fila de tarefas assíncrona ainda está se atualizando. Como resultado, algumas coisas em Rippling - como membros de grupo - pode ser obsoleto até que os empregos restantes alcançar nas próximas horas.

4. 28 Gouere 2026 da 02:09 UTCresolved

   O acesso ao aplicativo Rippling foi totalmente restaurado.

Traduzido automaticamente da atualização oficial do incidente.

1. 27 Gouere 2026 da 16:11 UTCinvestigating

   Estamos investigando problemas onde os usuários são incapazes de acessar o Rippling web e aplicativos móveis. Forneceremos uma atualização nos próximos 10 minutos.

2. 27 Gouere 2026 da 16:23 UTCinvestigating

   Estamos no meio da última missão. O desempenho permanece degradado enquanto o retorno está em movimento. Próxima atualização em 10 minutos.

3. 27 Gouere 2026 da 16:32 UTCinvestigating

   O acesso ao aplicativo Rippling é restaurado. Estamos monitorando a saúde e desempenho do local.

4. 27 Gouere 2026 da 17:08 UTCinvestigating

   O incidente é atenuado, já que as métricas de desempenho do aplicativo estão de volta aos níveis normais.

5. 27 Gouere 2026 da 18:37 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 16 Gouere 2026 da 09:44 UTCresolved

   O Rippling exibiu "Acesso negado" para alguns usuários acessando o Rippling. A questão foi totalmente atenuada e Rippling está totalmente operacional novamente.

Traduzido automaticamente da atualização oficial do incidente.

1. 10 Gouere 2026 da 17:37 UTCinvestigating

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

2. 10 Gouere 2026 da 18:54 UTCresolved

   This incident has been resolved.

1. 7 Gouere 2026 da 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 Gouere 2026 da 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 Gouere 2026 da 19:06 UTCresolved

   This incident has been resolved.

1. 24 Mezheven 2026 da 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 Mezheven 2026 da 19:31 UTCinvestigating

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

3. 24 Mezheven 2026 da 20:10 UTCmonitoring

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

4. 24 Mezheven 2026 da 20:56 UTCresolved

   This incident has been resolved.

1. 22 Mezheven 2026 da 15:46 UTCidentified

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

2. 22 Mezheven 2026 da 16:24 UTCresolved

   This incident has been resolved.

1. 19 Mezheven 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 20:27 UTCresolved

   This incident has been resolved.

1. 1 Mezheven 2026 da 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 Mezheven 2026 da 16:50 UTCmonitoring

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

3. 1 Mezheven 2026 da 21:48 UTCresolved

   This incident has been resolved.

1. 28 Mae 2026 da 16:16 UTCinvestigating

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

2. 28 Mae 2026 da 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 Mae 2026 da 16:47 UTCinvestigating

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

4. 28 Mae 2026 da 17:04 UTCinvestigating

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

5. 28 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 14:01 UTCmonitoring

   Error rates down, continuing to monitor

3. 27 Mae 2026 da 14:32 UTCresolved

   This incident has been resolved.

1. 18 Mae 2026 da 22:34 UTCinvestigating

   Users are reporting slowness while using Rippling

2. 19 Mae 2026 da 00:37 UTCidentified

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

3. 19 Mae 2026 da 00:40 UTCmonitoring

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

4. 19 Mae 2026 da 00:59 UTCresolved

   This incident has been resolved.

1. 14 Mae 2026 da 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 Mae 2026 da 20:58 UTCresolved

   The issue has been resolved

1. 6 Mae 2026 da 05:49 UTCinvestigating

   Rippling AI is down. We are investigating the issue.

2. 6 Mae 2026 da 05:54 UTCmonitoring

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

3. 6 Mae 2026 da 06:09 UTCresolved

   Rippling AI access has been restored.

1. 1 Mae 2026 da 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 Mae 2026 da 20:54 UTCmonitoring

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

3. 1 Mae 2026 da 20:54 UTCresolved

   This incident has been resolved.