Störungsverlauf von Replicon

1. 3. September 2026 um 10:38 UTCinvestigating

   Wir haben ein Problem identifiziert, das unsere Polaris-Dienste betrifft und sich auf mehrere Anwendungsbereiche auswirkt, darunter Timesheet, Time Off, Expense und Scheduling. Unsere Engineering-Teams untersuchen das Problem aktiv und werden weitere Updates bereitstellen, sobald mehr Informationen verfügbar sind.

2. 3. September 2026 um 10:55 UTCinvestigating

   Wir werden dieses Problem weiter untersuchen.

3. 3. September 2026 um 11:36 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

4. 3. September 2026 um 11:45 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

5. 3. September 2026 um 11:57 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 24. Juli 2026 um 15:52 UTCresolved

   Zwischen 4:48 Uhr und 5:09 Uhr MST (11:48-12:09 Uhr UTC) am 24. Juli 2026 können beim Zugriff auf unsere Dienste Konnektivitätsprobleme aufgetreten sein, einschließlich des Logins, wobei einige Anfragen HTTP 522 (Connection Timed Out) zurückgeben. Dies wurde durch einen Ausfall auf der Plattform unseres CDN-Anbieters verursacht. Unser Anbieter identifizierte und löste das Problem um 5:09 Uhr MST, und der Service wurde zu diesem Zeitpunkt vollständig wiederhergestellt.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 29. Juni 2026 um 13:49 UTCinvestigating

   Wir untersuchen derzeit ein Problem, das sich auf eine Teilmenge von Integrationen auswirkt, die auf unserer Integrationsplattform gehostet werden. Unsere Engineering-Teams arbeiten aktiv daran, die Ursache zu identifizieren und das Problem so schnell wie möglich zu lösen. Wir werden Updates bereitstellen, sobald wir weitere Informationen haben.

2. 29. Juni 2026 um 13:49 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

3. 29. Juni 2026 um 16:09 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 29. Juni 2026 um 17:09 UTCmonitoring

   Wir werden weiterhin auf weitere Probleme achten.

5. 30. Juni 2026 um 04:45 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 15. Juni 2026 um 23:50 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. 16. Juni 2026 um 00:06 UTCidentified

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

3. 16. Juni 2026 um 00:58 UTCmonitoring

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

4. 16. Juni 2026 um 02:30 UTCresolved

   This incident has been resolved.

1. 24. März 2026 um 18:51 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. 24. März 2026 um 18:52 UTCinvestigating

   We are continuing to investigate this issue.

3. 24. März 2026 um 18:54 UTCresolved

   This incident has been resolved.

1. 2. Februar 2026 um 15:37 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. 2. Februar 2026 um 16:07 UTCinvestigating

   We are continuing to investigate this issue.

3. 2. Februar 2026 um 16:53 UTCmonitoring

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

4. 2. Februar 2026 um 17:10 UTCresolved

   This incident has been resolved.

1. 19. Januar 2026 um 08:52 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. 19. Januar 2026 um 09:23 UTCinvestigating

   We are continuing to investigate this issue.

3. 19. Januar 2026 um 10:24 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. 19. Januar 2026 um 10:46 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. 19. Januar 2026 um 11:17 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. 19. Januar 2026 um 12:12 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 19. Januar 2026 um 12:48 UTCresolved

   This incident has been resolved.

1. 24. März 2026 um 18:57 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. 24. März 2026 um 19:00 UTCresolved

   This incident has been resolved.

1. 5. Dezember 2025 um 09:11 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. 5. Dezember 2025 um 09:18 UTCidentified

   The issue is identified by our edge network provider.

3. 5. Dezember 2025 um 09:22 UTCmonitoring

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

4. 5. Dezember 2025 um 10:18 UTCresolved

   This incident has been resolved.

1. 20. November 2025 um 14:43 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. 20. November 2025 um 15:22 UTCinvestigating

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

3. 20. November 2025 um 15:32 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. 20. November 2025 um 16:47 UTCidentified

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

5. 20. November 2025 um 17:17 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. 20. November 2025 um 17:35 UTCresolved

   This incident has been resolved.

1. 18. November 2025 um 12:29 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. 18. November 2025 um 13:22 UTCinvestigating

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

3. 18. November 2025 um 13:37 UTCinvestigating

   We are continuing to investigate this issue.

4. 18. November 2025 um 14:10 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. 18. November 2025 um 15:00 UTCmonitoring

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

6. 18. November 2025 um 15:56 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 18. November 2025 um 17:47 UTCresolved

   This incident has been resolved.

1. 20. Oktober 2025 um 10:37 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. 20. Oktober 2025 um 13:29 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. 20. Oktober 2025 um 15:57 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 20. Oktober 2025 um 18:41 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. 20. Oktober 2025 um 22:45 UTCmonitoring

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

6. 20. Oktober 2025 um 22:58 UTCresolved

   This incident has been resolved.

1. 6. Oktober 2025 um 06:31 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. 6. Oktober 2025 um 07:09 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. 6. Oktober 2025 um 07:32 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. 6. Oktober 2025 um 08:32 UTCinvestigating

   We are continuing to investigate this issue.

5. 6. Oktober 2025 um 09:32 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. 6. Oktober 2025 um 10:54 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. 6. Oktober 2025 um 12:29 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. 6. Oktober 2025 um 14:59 UTCmonitoring

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

9. 6. Oktober 2025 um 16:04 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. 6. Oktober 2025 um 17:15 UTCresolved

    This incident has been resolved.

1. 30. März 2025 um 18:25 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. 30. März 2025 um 18:38 UTCmonitoring

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

3. 30. März 2025 um 23:57 UTCresolved

   This incident has been resolved.

1. 22. März 2025 um 19:04 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. 22. März 2025 um 19:47 UTCidentified

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

3. 22. März 2025 um 20:40 UTCmonitoring

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

4. 23. März 2025 um 15:23 UTCresolved

   This incident has been resolved.

1. 15. März 2025 um 14:41 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. 15. März 2025 um 15:51 UTCinvestigating

   We are continuing to investigate this issue.

3. 15. März 2025 um 16:05 UTCmonitoring

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

4. 15. März 2025 um 16:57 UTCresolved

   This incident has been resolved.

1. 3. März 2025 um 15:25 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. 3. März 2025 um 15:52 UTCidentified

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

3. 3. März 2025 um 17:17 UTCidentified

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

4. 3. März 2025 um 17:42 UTCmonitoring

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

5. 3. März 2025 um 18:05 UTCresolved

   This incident has been resolved.

1. 7. Februar 2025 um 08:04 UTCinvestigating

   We are currently investigating this issue.

2. 7. Februar 2025 um 10:00 UTCidentified

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

3. 7. Februar 2025 um 10:06 UTCmonitoring

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

4. 7. Februar 2025 um 10:16 UTCresolved

   This incident has been resolved.

1. 24. Januar 2025 um 11:06 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. 24. Januar 2025 um 11:24 UTCidentified

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

3. 24. Januar 2025 um 14:39 UTCidentified

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

4. 24. Januar 2025 um 20:50 UTCresolved

   This incident has been resolved.

1. 23. Januar 2025 um 14:49 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. 23. Januar 2025 um 15:16 UTCidentified

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

3. 23. Januar 2025 um 15:51 UTCmonitoring

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

4. 23. Januar 2025 um 17:06 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 23. Januar 2025 um 19:51 UTCresolved

   This incident has been resolved.