54 Glia incidents · 2024년 1월 — official updates, affected components, duration and resolution details.
우리는 우리의 telephony 공급자와 협력하여 음성 상호 작용의 작은 비율에 영향을 미치는 문제를 해결합니다. 모든 디지털 채널은 완전히 작동 및 비범죄 유지.
문제는 확인되고 우리는 문제를 해결하기 위해 우리의 공급자와 긴급하게 일하고 있습니다.
납품업자는 그들의 끝에 문제점을 확인했습니다. 우리는 그들을 계속.
수정은 우리의 공급자에게서 실행되고 우리는 그것을 복구로 체계를 감시하고 있습니다. 우리는 문제를 감시하는 것을 계속합니다.
이 사건은 해결되었습니다.
공식 인시던트 업데이트를 자동 번역했습니다.
우리는 현재 참여의 성능에 영향을 미치는 문제점을 조사하고 있습니다. 이 문제를 해결하기 위해 노력하고 있습니다. 업데이트 된 정보를 최대한 빨리 공유합니다.
우리는 수정을 구현하고 복구로 시스템을 모니터링합니다. 우리는 문제를 감시하는 것을 계속합니다.
사건은 해결되었습니다, 우리의 telemetry 및 감시는 모든 특징이 완전히 기능한다는 것을 보여줍니다.
공식 인시던트 업데이트를 자동 번역했습니다.
우리는 현재 Glia 성과의 잠재적인 degradation를 투자하고 있습니다. 이 문제를 해결하기 위해 노력하고 있습니다.
팀은 높은 우선 순위를 가진 현재 성과 degradation를 조사하기 위하여 계속됩니다. 우리의 발견은 운영자 가용성에 영향을 미치고 참여 국가의 정확한보고를 나타냅니다.
우리는 수정을 구현하고 복구로 시스템을 모니터링합니다. 우리는 문제를 감시하는 것을 계속합니다.
사건은 모든 인스턴스를 완전하게 해결하고 예상대로 수행되었습니다.
공식 인시던트 업데이트를 자동 번역했습니다.
우리의 서비스 공급자는 Virtual Assistant에 영향을 미치는 서비스 중단을 보고했습니다. 우리는 우리의 서비스 제공 업체와 긴밀하게 협력하여 사건과 개발 문제를 해결합니다. 감사합니다.
우리는 우리의 서비스 공급자와 소통을 계속하여 사건을 밀접하게 감시하고 그(것)들을 해결하기 위하여 발달을 따릅니다.
서비스 제공 업체는 서비스 복원 및 Virtual Assistant가 예상대로 작동했다고보고했습니다.
공식 인시던트 업데이트를 자동 번역했습니다.
We are currently investigating an elevated number of errors in our telemetry. We are working to solve this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
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!
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.
The problem that was causing GVAs to experience intermittent failures has now been fully resolved and all services are fully operational. Thank you!
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.
Our telemetry shows that all systems are fully operational. We are continuing to monitor the issue.
Glia is fully operational and the incident is resolved.
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.
We continue to communicate with our service provider to monitor the incident closely and follow their developments to fix it.
Our service provider has reported that service has been restored, our telemetry and monitoring shows that Glia works as expected.
A small number of users are unable to end engagements due to the post-engagement survey not closing.
The issue has been indentified and a fix has been implemented.
We are currently monitoring the results to ensure that engagements are fully functional.
We have verified that the post-engagement surveys are now working as intended.
We are investigating a small number of transferred engagements that do not end for the visitor once the operator has ended them.
We continue to investigate. The impact is minimal, causing a few engagements that need to be ended by the visitor.
The root cause has been identified and all engagements are fully functional.
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.
The incident has been resolved, our telemetry shows that all features continue to be fully functional.
We are currently investigating an issue affecting the performance of the Cortex AI features.
Our team has identified this issue and is currently monitoring the behavior for further updates.
Our team continues to monitor system behavior. Forecast Analyst, Cortex Wrap-Up, and Cortex Heads-Up are fully operational.
This incident has been resolved. All Cortex AI services are fully operational.
We are currently investigating an elevated number of errors in our telemetry with Cortex AI. We are working to solve this issue.
This incident has been resolved.
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.
This incident has been resolved.
The system is recovering. Our engineering team is working on clearing out stuck engagements. Our expected time to completion is 20 min.
We have implemented a fix and are monitoring the system as it recovers. We are continuing to monitor the issue.
The incident has been fully resolved with all instances fully functional and performing as expected.
We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status).
We are continuing to investigate this issue.
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).
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).
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).
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).
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).
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).
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).
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).
We continue to communicate with our service provider to monitor the incident closely and follow their developments to fix it.
Our service provider has reported that service has been restored, telemetry and monitoring shows that Glia Engagement Routing works as expected.
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.
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.
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).
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).
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).
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).
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).
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).
We continue to communicate with our service provider to monitor the incident closely and follow their developments to fix it.
Our service provider has reported that service has been restored, telemetry and monitoring shows that Glia Phone services works as expected.
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.
We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status).
We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status).
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).
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).
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).
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).
We continue to communicate with our service provider to monitor the incident closely and follow their developments to fix it.
Our service provider has reported that service has been restored, telemetry and monitoring shows that Cortex AI services works as expected.
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.
We are continuing to investigate this issue.
We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status).
We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status).
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).
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).
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).
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).
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).
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).
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).
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).
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.
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.
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.
We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status).
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).
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).
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).
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).
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).
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).
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).
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).
Our service provider has reported that service has been restored, telemetry and monitoring shows that Glia SMS Services work as expected.
