Glia 장애 기록

1. 2026년 9월 1일 PM 4:44 UTCinvestigating

   우리는 우리의 telephony 공급자와 협력하여 음성 상호 작용의 작은 비율에 영향을 미치는 문제를 해결합니다. 모든 디지털 채널은 완전히 작동 및 비범죄 유지.

2. 2026년 9월 1일 PM 4:51 UTCidentified

   문제는 확인되고 우리는 문제를 해결하기 위해 우리의 공급자와 긴급하게 일하고 있습니다.

3. 2026년 9월 1일 PM 5:17 UTCidentified

   납품업자는 그들의 끝에 문제점을 확인했습니다. 우리는 그들을 계속.

4. 2026년 9월 1일 PM 5:35 UTCmonitoring

   수정은 우리의 공급자에게서 실행되고 우리는 그것을 복구로 체계를 감시하고 있습니다. 우리는 문제를 감시하는 것을 계속합니다.

5. 2026년 9월 1일 PM 5:38 UTCresolved

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

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

1. 2026년 8월 31일 PM 5:29 UTCinvestigating

   우리는 현재 참여의 성능에 영향을 미치는 문제점을 조사하고 있습니다. 이 문제를 해결하기 위해 노력하고 있습니다. 업데이트 된 정보를 최대한 빨리 공유합니다.

2. 2026년 8월 31일 PM 5:38 UTCmonitoring

   우리는 수정을 구현하고 복구로 시스템을 모니터링합니다. 우리는 문제를 감시하는 것을 계속합니다.

3. 2026년 8월 31일 PM 5:43 UTCresolved

   사건은 해결되었습니다, 우리의 telemetry 및 감시는 모든 특징이 완전히 기능한다는 것을 보여줍니다.

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

1. 2026년 8월 28일 PM 9:12 UTCinvestigating

   우리는 현재 Glia 성과의 잠재적인 degradation를 투자하고 있습니다. 이 문제를 해결하기 위해 노력하고 있습니다.

2. 2026년 8월 28일 PM 10:26 UTCinvestigating

   팀은 높은 우선 순위를 가진 현재 성과 degradation를 조사하기 위하여 계속됩니다. 우리의 발견은 운영자 가용성에 영향을 미치고 참여 국가의 정확한보고를 나타냅니다.

3. 2026년 8월 28일 PM 10:39 UTCmonitoring

   우리는 수정을 구현하고 복구로 시스템을 모니터링합니다. 우리는 문제를 감시하는 것을 계속합니다.

4. 2026년 8월 28일 PM 10:50 UTCresolved

   사건은 모든 인스턴스를 완전하게 해결하고 예상대로 수행되었습니다.

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

1. 2026년 8월 3일 PM 9:58 UTCinvestigating

   우리의 서비스 공급자는 Virtual Assistant에 영향을 미치는 서비스 중단을 보고했습니다. 우리는 우리의 서비스 제공 업체와 긴밀하게 협력하여 사건과 개발 문제를 해결합니다. 감사합니다.

2. 2026년 8월 3일 PM 10:28 UTCmonitoring

   우리는 우리의 서비스 공급자와 소통을 계속하여 사건을 밀접하게 감시하고 그(것)들을 해결하기 위하여 발달을 따릅니다.

3. 2026년 8월 3일 PM 10:54 UTCresolved

   서비스 제공 업체는 서비스 복원 및 Virtual Assistant가 예상대로 작동했다고보고했습니다.

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

1. 2026년 6월 24일 PM 5:10 UTCinvestigating

   We are currently investigating an elevated number of errors in our telemetry. We are working to solve this issue.

2. 2026년 6월 24일 PM 5:11 UTCidentified

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

3. 2026년 6월 24일 PM 5:11 UTCmonitoring

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

4. 2026년 6월 24일 PM 5:22 UTCresolved

   This incident has been resolved.

1. 2026년 6월 10일 PM 3:37 UTCinvestigating

   We are seeing high error rates from the Banking Flows when attempting to authenticate users via GVA. Users could be experiencing intermittent failures. We are aware of the issue and are working on a fix to remediate the issue. Thank you for your patience.

2. 2026년 6월 10일 PM 4:06 UTCidentified

   The problem that is causing GVAs to experiencing intermittent failures has now been identified and our team is working on a fix to address it. We continue on this. Thank you for your continued patience!

3. 2026년 6월 10일 PM 4:49 UTCmonitoring

   We have implemented a fix and our telemetry shows that all systems are fully operational. We are actively monitoring the fix deployment to confirm this has been resolved.

4. 2026년 6월 10일 PM 5:20 UTCresolved

   The problem that was causing GVAs to experience intermittent failures has now been fully resolved and all services are fully operational. Thank you!

1. 2026년 5월 8일 AM 1:20 UTCidentified

   We are experiencing an elevated rate of errors and users could be experiencing intermittent failures with reporting. We are aware of the issue and are working on a fix to remediate the issue.

2. 2026년 5월 8일 AM 2:05 UTCmonitoring

   Our telemetry shows that all systems are fully operational. We are continuing to monitor the issue.

3. 2026년 5월 8일 AM 2:12 UTCresolved

   Glia is fully operational and the incident is resolved.

1. 2026년 5월 8일 AM 12:37 UTCidentified

   Our service provider has reported service disruption affecting Glia Platform. We are communicating with our service provider and closely monitoring the incident and their developments to fix it.

2. 2026년 5월 8일 AM 1:15 UTCmonitoring

   We continue to communicate with our service provider to monitor the incident closely and follow their developments to fix it.

3. 2026년 5월 8일 AM 1:47 UTCresolved

   Our service provider has reported that service has been restored, our telemetry and monitoring shows that Glia works as expected.

1. 2026년 1월 19일 PM 1:17 UTCinvestigating

   A small number of users are unable to end engagements due to the post-engagement survey not closing.

2. 2026년 1월 19일 PM 1:28 UTCidentified

   The issue has been indentified and a fix has been implemented.

3. 2026년 1월 19일 PM 1:35 UTCmonitoring

   We are currently monitoring the results to ensure that engagements are fully functional.

4. 2026년 1월 19일 PM 1:43 UTCresolved

   We have verified that the post-engagement surveys are now working as intended.

1. 2025년 12월 11일 PM 1:47 UTCinvestigating

   We are investigating a small number of transferred engagements that do not end for the visitor once the operator has ended them.

2. 2025년 12월 11일 PM 3:08 UTCinvestigating

   We continue to investigate. The impact is minimal, causing a few engagements that need to be ended by the visitor.

3. 2025년 12월 11일 PM 6:14 UTCresolved

   The root cause has been identified and all engagements are fully functional.

1. 2025년 12월 3일 PM 4:49 UTCmonitoring

   There was an elevated number of errors affecting a small number of Phone GVA interactions. The operations team has taken actions to address these issues, and our telemetry shows that all phone GVA interactions are now working as expected. We are continuing to monitor the issue.

2. 2025년 12월 3일 PM 4:55 UTCresolved

   The incident has been resolved, our telemetry shows that all features continue to be fully functional.

1. 2025년 11월 3일 PM 6:12 UTCinvestigating

   We are currently investigating an issue affecting the performance of the Cortex AI features.

2. 2025년 11월 3일 PM 7:09 UTCmonitoring

   Our team has identified this issue and is currently monitoring the behavior for further updates.

3. 2025년 11월 3일 PM 7:29 UTCmonitoring

   Our team continues to monitor system behavior. Forecast Analyst, Cortex Wrap-Up, and Cortex Heads-Up are fully operational.

4. 2025년 11월 3일 PM 7:44 UTCresolved

   This incident has been resolved. All Cortex AI services are fully operational.

1. 2025년 10월 21일 PM 2:42 UTCinvestigating

   We are currently investigating an elevated number of errors in our telemetry with Cortex AI. We are working to solve this issue.

2. 2025년 10월 21일 PM 2:48 UTCresolved

   This incident has been resolved.

1. 2025년 10월 20일 PM 11:33 UTCmonitoring

   Our team has confirmed that all data is available and is actively being processed. Some customers may experience minor delays in viewing their processed data. Our systems continue to work through all outstanding information to ensure full completion.

2. 2025년 10월 21일 AM 6:51 UTCresolved

   This incident has been resolved.

1. 2025년 10월 20일 PM 10:35 UTCidentified

   The system is recovering. Our engineering team is working on clearing out stuck engagements. Our expected time to completion is 20 min.

2. 2025년 10월 20일 PM 10:38 UTCmonitoring

   We have implemented a fix and are monitoring the system as it recovers. We are continuing to monitor the issue.

3. 2025년 10월 20일 PM 10:57 UTCresolved

   The incident has been fully resolved with all instances fully functional and performing as expected.

1. 2025년 10월 20일 PM 4:35 UTCinvestigating

   We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status).

2. 2025년 10월 20일 PM 4:38 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025년 10월 20일 PM 5:01 UTCinvestigating

   Our investigation is continuing. This service issue is tied to the current AWS incident. See the AWS status page for details: (https://health.aws.amazon.com/health/status).

4. 2025년 10월 20일 PM 5:35 UTCinvestigating

   We're still actively investigating this issue. The service interruption is connected to the ongoing AWS incident you can track here: (https://health.aws.amazon.com/health/status).

5. 2025년 10월 20일 PM 6:09 UTCinvestigating

   Our service interruption stems from the ongoing AWS incident, and we are actively investigating its impact. For real-time updates, please follow the AWS status page here: (https://health.aws.amazon.com/health/status).

6. 2025년 10월 20일 PM 6:31 UTCinvestigating

   We're continuing our investigation into the specific impact on our service. The service interruption is connected to the ongoing, widespread AWS incident. You can monitor the official AWS status page here: (https://health.aws.amazon.com/health/status).

7. 2025년 10월 20일 PM 7:03 UTCinvestigating

   We are continuing to assess the extent of the disruption. The service interruption is associated with the reported AWS platform incident. We advise tracking the broader situation via the official AWS status page: (https://health.aws.amazon.com/health/status).

8. 2025년 10월 20일 PM 7:35 UTCinvestigating

   We are actively reviewing our systems in light of the current AWS incident. This issue is directly related to that event. For updates on the overall situation, please refer to the AWS status page here: (https://health.aws.amazon.com/health/status).

9. 2025년 10월 20일 PM 7:51 UTCinvestigating

   The team is starting to see the system recover. AWS is currently throttling the speed of requests which adversely impacts real-time systems. We are in active communication with AWS and their engineers are on the line with our team. You can monitor the official AWS status page here: (https://health.aws.amazon.com/health/status).

10. 2025년 10월 20일 PM 8:37 UTCinvestigating

    We are actively assessing the specific scope of this service interruption. We have confirmed a clear link to the current, widespread AWS operational incident. Please refer to the official AWS status page for updates on the overarching issue: (https://health.aws.amazon.com/health/status).

11. 2025년 10월 20일 PM 8:40 UTCmonitoring

    We continue to communicate with our service provider to monitor the incident closely and follow their developments to fix it.

12. 2025년 10월 20일 PM 9:08 UTCresolved

    Our service provider has reported that service has been restored, telemetry and monitoring shows that Glia Engagement Routing works as expected.

1. 2025년 10월 20일 PM 2:20 UTCinvestigating

   Our Phone Service Provider has reported service disruption affecting phone engagements. We are communicating and monitoring closely the incident and the developments to fix it.

2. 2025년 10월 20일 PM 3:30 UTCidentified

   Our Phone Service Provider has reported intermittent service disruption related to an ongoing AWS incident (https://health.aws.amazon.com/health/status) affecting phone engagements. We are communicating with our service provider and closely monitoring the incident and their developments to fix it.

3. 2025년 10월 20일 PM 5:00 UTCidentified

   Our investigation is continuing. This service issue is tied to the current AWS incident. See the AWS status page for details: (https://health.aws.amazon.com/health/status).

4. 2025년 10월 20일 PM 5:35 UTCidentified

   We're still actively investigating this issue. The service interruption is connected to the ongoing AWS incident you can track here: (https://health.aws.amazon.com/health/status).

5. 2025년 10월 20일 PM 6:09 UTCidentified

   Our service interruption stems from the ongoing AWS incident, and we are actively investigating its impact. For real-time updates, please follow the AWS status page here: (https://health.aws.amazon.com/health/status).

6. 2025년 10월 20일 PM 6:32 UTCidentified

   We're continuing our investigation into the specific impact on our service. The service interruption is connected to the ongoing, widespread AWS incident. You can monitor the official AWS status page here: (https://health.aws.amazon.com/health/status).

7. 2025년 10월 20일 PM 7:03 UTCidentified

   We are continuing to assess the extent of the disruption. The service interruption is associated with the reported AWS platform incident. We advise tracking the broader situation via the official AWS status page: (https://health.aws.amazon.com/health/status).

8. 2025년 10월 20일 PM 7:35 UTCidentified

   We are actively reviewing our systems in light of the current AWS incident. This issue is directly related to that event. For updates on the overall situation, please refer to the AWS status page here: (https://health.aws.amazon.com/health/status).

9. 2025년 10월 20일 PM 8:06 UTCmonitoring

   We continue to communicate with our service provider to monitor the incident closely and follow their developments to fix it.

10. 2025년 10월 20일 PM 8:42 UTCresolved

    Our service provider has reported that service has been restored, telemetry and monitoring shows that Glia Phone services works as expected.

1. 2025년 10월 20일 PM 2:09 UTCinvestigating

   We are currently investigating an issue affecting the performance of the Cortex AI features. Agents are able to connect with customers via chat, audio, video. We are working to resolve this issue. We will share updated info here as soon as possible.

2. 2025년 10월 20일 PM 2:46 UTCidentified

   We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status).

3. 2025년 10월 20일 PM 3:29 UTCinvestigating

   We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status).

4. 2025년 10월 20일 PM 5:00 UTCinvestigating

   Our investigation is continuing. This service issue is tied to the current AWS incident. See the AWS status page for details: (https://health.aws.amazon.com/health/status).

5. 2025년 10월 20일 PM 5:34 UTCinvestigating

   We're still actively investigating this issue. The service interruption is connected to the ongoing AWS incident you can track here: (https://health.aws.amazon.com/health/status).

6. 2025년 10월 20일 PM 6:10 UTCinvestigating

   Our service interruption stems from the ongoing AWS incident, and we are actively investigating its impact. For real-time updates, please follow the AWS status page here: (https://health.aws.amazon.com/health/status).

7. 2025년 10월 20일 PM 6:32 UTCinvestigating

   We're continuing our investigation into the specific impact on our service. The service interruption is connected to the ongoing, widespread AWS incident. You can monitor the official AWS status page here: (https://health.aws.amazon.com/health/status).

8. 2025년 10월 20일 PM 6:56 UTCmonitoring

   We continue to communicate with our service provider to monitor the incident closely and follow their developments to fix it.

9. 2025년 10월 20일 PM 7:45 UTCresolved

   Our service provider has reported that service has been restored, telemetry and monitoring shows that Cortex AI services works as expected.

1. 2025년 10월 20일 PM 1:36 UTCinvestigating

   We are currently investigating an issue affecting the performance of Insights. We are working to resolve this issue. We will share updated info here as soon as possible.

2. 2025년 10월 20일 PM 1:37 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025년 10월 20일 PM 2:45 UTCidentified

   We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status).

4. 2025년 10월 20일 PM 3:29 UTCinvestigating

   We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status).

5. 2025년 10월 20일 PM 5:00 UTCinvestigating

   Our investigation is continuing. This service issue is tied to the current AWS incident. See the AWS status page for details: (https://health.aws.amazon.com/health/status).

6. 2025년 10월 20일 PM 6:33 UTCinvestigating

   We're continuing our investigation into the specific impact on our service. The service interruption is connected to the ongoing, widespread AWS incident. You can monitor the official AWS status page here: (https://health.aws.amazon.com/health/status).

7. 2025년 10월 20일 PM 7:03 UTCinvestigating

   We are continuing to assess the extent of the disruption. The service interruption is associated with the reported AWS platform incident. We advise tracking the broader situation via the official AWS status page: (https://health.aws.amazon.com/health/status).

8. 2025년 10월 20일 PM 7:36 UTCinvestigating

   We are actively reviewing our systems in light of the current AWS incident. This issue is directly related to that event. For updates on the overall situation, please refer to the AWS status page here: (https://health.aws.amazon.com/health/status).

9. 2025년 10월 20일 PM 8:02 UTCinvestigating

   Our team is conducting internal diagnostics to assess the exact impact on our service. This interruption is associated with the current AWS operational event. The overall status of the incident can be monitored here: (https://health.aws.amazon.com/health/status).

10. 2025년 10월 20일 PM 8:37 UTCinvestigating

    We are actively assessing the specific scope of this service interruption. We have confirmed a clear link to the current, widespread AWS operational incident. Please refer to the official AWS status page for updates on the overarching issue: (https://health.aws.amazon.com/health/status).

11. 2025년 10월 20일 PM 9:38 UTCinvestigating

    We're still actively investigating this issue. The service interruption is connected to the ongoing AWS incident you can track here: (https://health.aws.amazon.com/health/status).

12. 2025년 10월 20일 PM 10:29 UTCinvestigating

    Our service interruption stems from the ongoing AWS incident, and we are actively investigating its impact. For real-time updates, please follow the AWS status page here: (https://health.aws.amazon.com/health/status).

13. 2025년 10월 20일 PM 11:30 UTCresolved

    Our team has confirmed that all data is available and is actively being processed. Some customers may experience minor delays in viewing their processed data. Our systems continue to work through all outstanding information to ensure full completion.

1. 2025년 10월 20일 AM 11:54 UTCidentified

   Our Phone Service Provider has reported service disruption affecting phone engagements. We are communicating and monitoring closely the incident and the developments to fix it.

2. 2025년 10월 20일 AM 11:58 UTCidentified

   Our Phone Service Provider has reported a service disruption affecting SMS engagements for our EU customers only. We are communicating closely with the provider and monitoring developments to fix the incident.

3. 2025년 10월 20일 PM 3:28 UTCidentified

   We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status).

4. 2025년 10월 20일 PM 4:59 UTCidentified

   Our investigation is continuing. This service issue is tied to the current AWS incident. See the AWS status page for details: (https://health.aws.amazon.com/health/status).

5. 2025년 10월 20일 PM 5:33 UTCidentified

   We're still actively investigating this issue. The service interruption is connected to the ongoing AWS incident you can track here: (https://health.aws.amazon.com/health/status).

6. 2025년 10월 20일 PM 6:10 UTCidentified

   Our service interruption stems from the ongoing AWS incident, and we are actively investigating its impact. For real-time updates, please follow the AWS status page here: (https://health.aws.amazon.com/health/status).

7. 2025년 10월 20일 PM 6:33 UTCidentified

   We're continuing our investigation into the specific impact on our service. The service interruption is connected to the ongoing, widespread AWS incident. You can monitor the official AWS status page here: (https://health.aws.amazon.com/health/status).

8. 2025년 10월 20일 PM 7:03 UTCidentified

   We are continuing to assess the extent of the disruption. The service interruption is associated with the reported AWS platform incident. We advise tracking the broader situation via the official AWS status page: (https://health.aws.amazon.com/health/status).

9. 2025년 10월 20일 PM 7:36 UTCidentified

   We are actively reviewing our systems in light of the current AWS incident. This issue is directly related to that event. For updates on the overall situation, please refer to the AWS status page here: (https://health.aws.amazon.com/health/status).

10. 2025년 10월 20일 PM 8:02 UTCidentified

    Our team is conducting internal diagnostics to assess the exact impact on our service. This interruption is associated with the current AWS operational event. The overall status of the incident can be monitored here: (https://health.aws.amazon.com/health/status).

11. 2025년 10월 20일 PM 8:37 UTCidentified

    We are actively assessing the specific scope of this service interruption. We have confirmed a clear link to the current, widespread AWS operational incident. Please refer to the official AWS status page for updates on the overarching issue: (https://health.aws.amazon.com/health/status).

12. 2025년 10월 20일 PM 9:42 UTCresolved

    Our service provider has reported that service has been restored, telemetry and monitoring shows that Glia SMS Services work as expected.