Historial de interrupciones de Replicon

1. September 3, 2026 at 10:38 AM UTCinvestigating

   Hemos identificado un problema que afecta a nuestros servicios Polaris, que está afectando múltiples áreas de aplicación, incluyendo Timesheet, Time Off, Expense y Programación. Nuestros equipos de ingeniería están investigando activamente la cuestión y proporcionarán nuevas actualizaciones a medida que se disponga de más información.

2. September 3, 2026 at 10:55 AM UTCinvestigating

   Seguimos investigando esta cuestión.

3. September 3, 2026 at 11:36 AM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

4. September 3, 2026 at 11:45 AM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

5. September 3, 2026 at 11:57 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 24, 2026 at 3:52 PM UTCresolved

   Entre las 4:48 AM y las 5:09 AM MST (11:48–12:09 UTC) el 24 de julio de 2026, los usuarios pueden haber experimentado problemas de conectividad al acceder a nuestros servicios, incluido el login, con algunas solicitudes de devolución HTTP 522 (Connection Timed Out). Esto fue causado por un outage en la plataforma de nuestro proveedor de CDN. Nuestro proveedor identificó y resolvió el tema a las 5:09 AM MST, y el servicio fue restaurado completamente en ese momento.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 29, 2026 at 1:49 PM UTCinvestigating

   Actualmente estamos investigando un problema que afecta a un subconjunto de integraciones alojadas en nuestra plataforma de integración. Nuestros equipos de ingeniería están trabajando activamente para identificar la causa raíz y resolver el problema lo antes posible. Proporcionaremos actualizaciones tan pronto como tengamos más información.

2. June 29, 2026 at 1:49 PM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. June 29, 2026 at 4:09 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. June 29, 2026 at 5:09 PM UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

5. June 30, 2026 at 4:45 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 15, 2026 at 11:50 PM UTCinvestigating

   We have noticed elevated errors impacting logins and access to our application for the tenants hosted on various swimlanes. Our Engineering teams are currently looking into the issue. We will post updates as soon as we have more information.

2. June 16, 2026 at 12:06 AM UTCidentified

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

3. June 16, 2026 at 12:58 AM UTCmonitoring

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

4. June 16, 2026 at 2:30 AM UTCresolved

   This incident has been resolved.

1. March 24, 2026 at 6:51 PM UTCinvestigating

   We are observing intermittent elevated error rates that may prevent users from viewing or updating their timesheets. Our engineering teams are actively investigating the issue and will provide further updates as more information becomes available

2. March 24, 2026 at 6:52 PM UTCinvestigating

   We are continuing to investigate this issue.

3. March 24, 2026 at 6:54 PM UTCresolved

   This incident has been resolved.

1. February 2, 2026 at 3:37 PM UTCinvestigating

   We are experiencing login slowness and elevated error rates when navigating between pages. Our engineering teams are actively investigating the issue and will provide further updates as more information becomes available.

2. February 2, 2026 at 4:07 PM UTCinvestigating

   We are continuing to investigate this issue.

3. February 2, 2026 at 4:53 PM UTCmonitoring

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

4. February 2, 2026 at 5:10 PM UTCresolved

   This incident has been resolved.

1. January 19, 2026 at 8:52 AM UTCinvestigating

   We are investigating a performance issue that is causing slower-than-usual timesheet submissions. Our engineering teams are actively working to identify and address the cause. We will provide further updates as more information becomes available.

2. January 19, 2026 at 9:23 AM UTCinvestigating

   We are continuing to investigate this issue.

3. January 19, 2026 at 10:24 AM UTCinvestigating

   We are observing slowness with logins and elevated error rates while navigating between pages. Our engineering teams are actively investigating the issue and will provide further updates as more information becomes available.

4. January 19, 2026 at 10:46 AM UTCinvestigating

   Login performance and elevated error rates have returned to normal. However, some users may still experience slowness when submitting timesheets. Our engineering teams are actively working to identify and address the cause. We will provide further updates as more information becomes available.

5. January 19, 2026 at 11:17 AM UTCmonitoring

   Login slowness and elevated error rates have recovered. Timesheet submission performance is showing improvement, and we are closely monitoring to ensure continued stability.

6. January 19, 2026 at 12:12 PM UTCmonitoring

   We are continuing to monitor for any further issues.

7. January 19, 2026 at 12:48 PM UTCresolved

   This incident has been resolved.

1. March 24, 2026 at 6:57 PM UTCinvestigating

   We are observing intermittent elevated error rates that may prevent users from viewing or updating their timesheets. Our engineering teams are actively investigating the issue and will provide further updates as more information becomes available

2. March 24, 2026 at 7:00 PM UTCresolved

   This incident has been resolved.

1. December 5, 2025 at 9:11 AM UTCinvestigating

   We are currently experiencing login failures. Our edge network provider is having an ongoing outage that is impacting our authentication services. We are working closely with the provider to mitigate the issue as soon as possible.

2. December 5, 2025 at 9:18 AM UTCidentified

   The issue is identified by our edge network provider.

3. December 5, 2025 at 9:22 AM UTCmonitoring

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

4. December 5, 2025 at 10:18 AM UTCresolved

   This incident has been resolved.

1. November 20, 2025 at 2:43 PM UTCinvestigating

   We are experiencing elevated errors that are impacting logins through ADP SSO. At this time, we do not yet know whether the issue is with our vendor. Our engineering teams are actively investigating, and we will provide further updates as more information becomes available.

2. November 20, 2025 at 3:22 PM UTCinvestigating

   We are working with our vendor and continuing to investigate the issue. Further updates will be shared as more information becomes available.

3. November 20, 2025 at 3:32 PM UTCidentified

   ADP Support has confirmed an issue on their end, and their investigation is currently in progress. We will share further updates as they become available.

4. November 20, 2025 at 4:47 PM UTCidentified

   We are still awaiting the next update from the ADP team. We will share more information as soon as it becomes available.

5. November 20, 2025 at 5:17 PM UTCmonitoring

   We have received confirmation from the ADP team that the issue has been fixed. We are currently monitoring the results to ensure full stability

6. November 20, 2025 at 5:35 PM UTCresolved

   This incident has been resolved.

1. November 18, 2025 at 12:29 PM UTCmonitoring

   NA10 environment experienced elevated errors affecting logins and application access between 11:30 AM and 12:10 PM UTC. The issue has now been resolved, and we are monitoring the system to ensure continued stability.

2. November 18, 2025 at 1:22 PM UTCinvestigating

   We are currently experiencing elevated errors again, impacting logins and access to our application. Our engineering teams are actively investigating the issue.

3. November 18, 2025 at 1:37 PM UTCinvestigating

   We are continuing to investigate this issue.

4. November 18, 2025 at 2:10 PM UTCidentified

   This disruption appears to be related to the ongoing https://www.cloudflarestatus.com/. We are working closely to mitigate the impact and will provide updates as soon as more information becomes available.

5. November 18, 2025 at 3:00 PM UTCmonitoring

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

6. November 18, 2025 at 3:56 PM UTCmonitoring

   We are continuing to monitor for any further issues.

7. November 18, 2025 at 5:47 PM UTCresolved

   This incident has been resolved.

1. October 20, 2025 at 10:37 AM UTCmonitoring

   Earlier today, AWS experienced an outage in one of its US East regions, impacting multiple AWS services as well as other platforms hosted on AWS. As a result, our status page was also temporarily unavailable, preventing us from posting timely updates. Starting at 7:10 AM UTC, we observed an elevated level of errors affecting customers hosted on our NA4, NA6, and NA8 tenant environments. This issue was directly related to the AWS outage. We are actively working with the AWS Support team to monitor their recovery efforts and ensure full service stability. Further updates will be shared as more information becomes available.

2. October 20, 2025 at 1:29 PM UTCmonitoring

   We are actively working with the AWS Support team to investigate and monitor their recovery efforts. Most services remain available, though some users may experience occasional disruptions. We are closely tracking progress to ensure full service stability and will share further updates as more information becomes available.

3. October 20, 2025 at 3:57 PM UTCmonitoring

   We are continuing to monitor for any further issues.

4. October 20, 2025 at 6:41 PM UTCmonitoring

   We continue to work with the AWS Support team as recovery efforts progress in the affected region. Most services remain available, though some users may still experience intermittent performance issues. We are closely monitoring the situation and will share further updates as recovery continues.

5. October 20, 2025 at 10:45 PM UTCmonitoring

   The system has now returned to normal operation. We are continuing to monitor for any further issues.

6. October 20, 2025 at 10:58 PM UTCresolved

   This incident has been resolved.

1. October 6, 2025 at 6:31 AM UTCinvestigating

   We are investigating a performance issue that is causing slower-than-usual logins and timesheet submissions. Our engineering teams are actively working on identifying the cause. We will provide further updates as soon as more information becomes available.

2. October 6, 2025 at 7:09 AM UTCinvestigating

   Login performance has recovered. However, some users may still experience slowness when navigating between pages. We are also continuing to work on resolving the issue with slow timesheet submissions. Further updates will be shared as progress is made.

3. October 6, 2025 at 7:32 AM UTCinvestigating

   We are currently investigating intermittent login failures. In parallel, our teams continue to work on resolving the ongoing issue with slow timesheet submissions. We will share further updates as they become available.

4. October 6, 2025 at 8:32 AM UTCinvestigating

   We are continuing to investigate this issue.

5. October 6, 2025 at 9:32 AM UTCinvestigating

   We are continuing to investigate this issue. Most services remain available, though some users may experience occasional disruptions. We are also continuing to work on resolving the issue with slow timesheet submissions. Further updates will be shared as they become available.

6. October 6, 2025 at 10:54 AM UTCinvestigating

   Logins remain stable, though some users may still experience intermittent slowness when navigating between pages. The system is gradually recovering. In parallel, our teams continue to work on resolving the issue with slow timesheet submissions.

7. October 6, 2025 at 12:29 PM UTCmonitoring

   The system is stable. We are currently working through backlogs related to background jobs and are closely monitoring progress. As these backlogs are cleared, timesheet submission performance is expected to improve and return to normal.

8. October 6, 2025 at 2:59 PM UTCmonitoring

   Backlogs have been cleared, and timesheet submission performance is gradually improving. We expect the system to return to normal very soon.

9. October 6, 2025 at 4:04 PM UTCmonitoring

   Backlogs have been cleared, and timesheet submission performance has improved. The system has returned to normal, and we are continuing to monitor for any further issues.

10. October 6, 2025 at 5:15 PM UTCresolved

    This incident has been resolved.

1. March 30, 2025 at 6:25 PM UTCinvestigating

   We are currently investigating an issue impacting a subset of integrations hosted on our integration platform. Our engineering teams are actively working on identifying the root cause and resolving the issue as quickly as possible. We will provide updates as soon as we have more information. For any questions or further assistance, please reach out to [email protected].

2. March 30, 2025 at 6:38 PM UTCmonitoring

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

3. March 30, 2025 at 11:57 PM UTCresolved

   This incident has been resolved.

1. March 22, 2025 at 7:04 PM UTCinvestigating

   We are currently investigating an issue impacting a subset of integrations hosted on our integration platform. Our engineering teams are actively working on identifying the root cause and resolving the issue as quickly as possible. We will provide updates as soon as we have more information.

2. March 22, 2025 at 7:47 PM UTCidentified

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

3. March 22, 2025 at 8:40 PM UTCmonitoring

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

4. March 23, 2025 at 3:23 PM UTCresolved

   This incident has been resolved.

1. March 15, 2025 at 2:41 PM UTCinvestigating

   We are currently investigating an issue impacting a subset of integrations hosted on our integration platform. Our engineering teams are actively working on identifying the root cause and resolving the issue as quickly as possible. We will provide updates as soon as we have more information. For any questions or further assistance, please reach out to [email protected].

2. March 15, 2025 at 3:51 PM UTCinvestigating

   We are continuing to investigate this issue.

3. March 15, 2025 at 4:05 PM UTCmonitoring

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

4. March 15, 2025 at 4:57 PM UTCresolved

   This incident has been resolved.

1. March 3, 2025 at 3:25 PM UTCinvestigating

   We are currently investigating elevated error rates affecting access to our application. Our Engineering teams are actively working on the issue, and we will provide updates as soon as more information becomes available.

2. March 3, 2025 at 3:52 PM UTCidentified

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

3. March 3, 2025 at 5:17 PM UTCidentified

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

4. March 3, 2025 at 5:42 PM UTCmonitoring

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

5. March 3, 2025 at 6:05 PM UTCresolved

   This incident has been resolved.

1. February 7, 2025 at 8:04 AM UTCinvestigating

   We are currently investigating this issue.

2. February 7, 2025 at 10:00 AM UTCidentified

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

3. February 7, 2025 at 10:06 AM UTCmonitoring

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

4. February 7, 2025 at 10:16 AM UTCresolved

   This incident has been resolved.

1. January 24, 2025 at 11:06 AM UTCinvestigating

   We are aware of elevated errors impacting login and access to our application. Our Engineering teams are actively investigating the issue and are working to resolve it as quickly as possible. We will provide updates as more information becomes available.

2. January 24, 2025 at 11:24 AM UTCidentified

   The root cause has been identified and working on a resolution to resolve this issue at the earliest.

3. January 24, 2025 at 2:39 PM UTCidentified

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

4. January 24, 2025 at 8:50 PM UTCresolved

   This incident has been resolved.

1. January 23, 2025 at 2:49 PM UTCidentified

   We have identified a performance degradation issue impacting backend processes, which has affected the accuracy of pre-calculated data displayed on certain list pages and reports. The root cause of this issue has been identified, and we are actively working on a resolution to address it at the earliest.

2. January 23, 2025 at 3:16 PM UTCidentified

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

3. January 23, 2025 at 3:51 PM UTCmonitoring

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

4. January 23, 2025 at 5:06 PM UTCmonitoring

   We are continuing to monitor for any further issues.

5. January 23, 2025 at 7:51 PM UTCresolved

   This incident has been resolved.