Replicon 장애 기록

1. 2026년 9월 3일 오전 10:38 UTCinvestigating

   우리는 Timesheet, Time Off, Expense 및 Scheduling을 포함한 여러 응용 분야에 영향을 미치는 Polaris 서비스에 영향을 미치는 문제점을 발견했습니다. 우리의 엔지니어링 팀은 적극적으로 문제를 투자하고 더 많은 정보를 제공 할 것입니다.

2. 2026년 9월 3일 오전 10:55 UTCinvestigating

   이 문제를 조사하고 있습니다.

3. 2026년 9월 3일 오전 11:36 UTCidentified

   문제는 식별되고 수정이 구현됩니다.

4. 2026년 9월 3일 오전 11:45 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

5. 2026년 9월 3일 오전 11:57 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 24일 오후 3:52 UTCresolved

   4:48 AM 및 5:09 AM MST (11:48–12:09 UTC) 7월 24, 2026, 사용자는 HTTP 522 (Connection Timed Out)을 반환 일부 요청과 같은 로그인을 포함하여 우리의 서비스에 액세스 할 때 연결 문제를 경험할 수 있습니다. 이것은 우리의 CDN 공급자의 플랫폼에 정전에 기인했습니다. 확인된 우리의 공급자는 5:09 AM MST에 문제점을 해결하고, 서비스는 그 시간에 완전히 복원되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 29일 오후 1:49 UTCinvestigating

   우리는 현재 통합 플랫폼에서 호스팅되는 통합의 하위 집합에 영향을 미치는 문제점을 조사하고 있습니다. 우리의 엔지니어링 팀은 뿌리 원인을 확인하고 가능한 한 빨리 문제를 해결하기 위해 적극적으로 노력하고 있습니다. 우리는 우리가 더 많은 정보가 있기 때문에 업데이트 제공 할 것입니다.

2. 2026년 6월 29일 오후 1:49 UTCidentified

   문제는 식별되고 수정이 구현됩니다.

3. 2026년 6월 29일 오후 4:09 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

4. 2026년 6월 29일 오후 5:09 UTCmonitoring

   우리는 더 많은 문제를 모니터링하고 있습니다.

5. 2026년 6월 30일 오전 4:45 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 15일 오후 11: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. 2026년 6월 16일 오전 12:06 UTCidentified

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

3. 2026년 6월 16일 오전 12:58 UTCmonitoring

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

4. 2026년 6월 16일 오전 2:30 UTCresolved

   This incident has been resolved.

1. 2026년 3월 24일 오후 6: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. 2026년 3월 24일 오후 6:52 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 3월 24일 오후 6:54 UTCresolved

   This incident has been resolved.

1. 2026년 2월 2일 오후 3: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. 2026년 2월 2일 오후 4:07 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 2월 2일 오후 4:53 UTCmonitoring

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

4. 2026년 2월 2일 오후 5:10 UTCresolved

   This incident has been resolved.

1. 2026년 1월 19일 오전 8: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. 2026년 1월 19일 오전 9:23 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 1월 19일 오전 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. 2026년 1월 19일 오전 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. 2026년 1월 19일 오전 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. 2026년 1월 19일 오후 12:12 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 2026년 1월 19일 오후 12:48 UTCresolved

   This incident has been resolved.

1. 2026년 3월 24일 오후 6: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. 2026년 3월 24일 오후 7:00 UTCresolved

   This incident has been resolved.

1. 2025년 12월 5일 오전 9: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. 2025년 12월 5일 오전 9:18 UTCidentified

   The issue is identified by our edge network provider.

3. 2025년 12월 5일 오전 9:22 UTCmonitoring

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

4. 2025년 12월 5일 오전 10:18 UTCresolved

   This incident has been resolved.

1. 2025년 11월 20일 오후 2: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. 2025년 11월 20일 오후 3: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. 2025년 11월 20일 오후 3: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. 2025년 11월 20일 오후 4: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. 2025년 11월 20일 오후 5: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. 2025년 11월 20일 오후 5:35 UTCresolved

   This incident has been resolved.

1. 2025년 11월 18일 오후 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. 2025년 11월 18일 오후 1: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. 2025년 11월 18일 오후 1:37 UTCinvestigating

   We are continuing to investigate this issue.

4. 2025년 11월 18일 오후 2: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. 2025년 11월 18일 오후 3:00 UTCmonitoring

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

6. 2025년 11월 18일 오후 3:56 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 2025년 11월 18일 오후 5:47 UTCresolved

   This incident has been resolved.

1. 2025년 10월 20일 오전 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. 2025년 10월 20일 오후 1: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. 2025년 10월 20일 오후 3:57 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2025년 10월 20일 오후 6: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. 2025년 10월 20일 오후 10:45 UTCmonitoring

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

6. 2025년 10월 20일 오후 10:58 UTCresolved

   This incident has been resolved.

1. 2025년 10월 6일 오전 6: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. 2025년 10월 6일 오전 7: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. 2025년 10월 6일 오전 7: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. 2025년 10월 6일 오전 8:32 UTCinvestigating

   We are continuing to investigate this issue.

5. 2025년 10월 6일 오전 9: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. 2025년 10월 6일 오전 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. 2025년 10월 6일 오후 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. 2025년 10월 6일 오후 2:59 UTCmonitoring

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

9. 2025년 10월 6일 오후 4: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. 2025년 10월 6일 오후 5:15 UTCresolved

    This incident has been resolved.

1. 2025년 3월 30일 오후 6: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. 2025년 3월 30일 오후 6:38 UTCmonitoring

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

3. 2025년 3월 30일 오후 11:57 UTCresolved

   This incident has been resolved.

1. 2025년 3월 22일 오후 7: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. 2025년 3월 22일 오후 7:47 UTCidentified

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

3. 2025년 3월 22일 오후 8:40 UTCmonitoring

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

4. 2025년 3월 23일 오후 3:23 UTCresolved

   This incident has been resolved.

1. 2025년 3월 15일 오후 2: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. 2025년 3월 15일 오후 3:51 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025년 3월 15일 오후 4:05 UTCmonitoring

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

4. 2025년 3월 15일 오후 4:57 UTCresolved

   This incident has been resolved.

1. 2025년 3월 3일 오후 3: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. 2025년 3월 3일 오후 3:52 UTCidentified

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

3. 2025년 3월 3일 오후 5:17 UTCidentified

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

4. 2025년 3월 3일 오후 5:42 UTCmonitoring

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

5. 2025년 3월 3일 오후 6:05 UTCresolved

   This incident has been resolved.

1. 2025년 2월 7일 오전 8:04 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 2월 7일 오전 10:00 UTCidentified

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

3. 2025년 2월 7일 오전 10:06 UTCmonitoring

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

4. 2025년 2월 7일 오전 10:16 UTCresolved

   This incident has been resolved.

1. 2025년 1월 24일 오전 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. 2025년 1월 24일 오전 11:24 UTCidentified

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

3. 2025년 1월 24일 오후 2:39 UTCidentified

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

4. 2025년 1월 24일 오후 8:50 UTCresolved

   This incident has been resolved.

1. 2025년 1월 23일 오후 2: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. 2025년 1월 23일 오후 3:16 UTCidentified

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

3. 2025년 1월 23일 오후 3:51 UTCmonitoring

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

4. 2025년 1월 23일 오후 5:06 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2025년 1월 23일 오후 7:51 UTCresolved

   This incident has been resolved.