54 Glia incidents · 2024年1月 — official updates, affected components, duration and resolution details.
我们正同我们的电话提供者积极合作,以解决影响一小部分语音互动的问题。 所有数字频道仍然全面运作,不受影响.
这个问题已经确定,我们正同我们的提供者紧急地合作来解决这个问题.
供应商已查明问题。 我们继续与他们合作.
我们的供应商已经实施了一个解决方案,我们正在监测该系统的恢复情况。 我们正在继续监测这一问题.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们目前正在调查一个影响工作表现的问题。 我们正在努力解决这一问题。 我们将尽快在这里分享最新资料.
我们实施了一项固定措施,并正在监测该系统的恢复情况。 我们正在继续监测这一问题.
这一事件已经得到解决,我们的遥测和监测显示,所有特征都充分发挥作用.
自动翻译自官方事件更新。
我们正在调查Glia的表现可能恶化的情况。 我们正在努力解决这一问题.
该小组正继续高度优先地调查目前业绩恶化的情况。 我们的调查结果表明,这影响到运营商的可用性和对业务约定状态的准确报告.
我们实施了一项固定措施,并正在监测该系统的恢复情况。 我们正在继续监测这一问题.
事件已经完全解决,所有事件都按预期全面运作和进行.
自动翻译自官方事件更新。
我们的服务提供商报告了影响虚拟助理的服务中断。 我们正在与我们的服务提供者进行沟通,并密切监测事件及其发展,以解决这一问题。 谢谢你的耐心.
我们继续与我们的服务供应商进行沟通,以密切监测这一事件并跟踪其事态发展,以解决这一问题.
我们的服务提供者报告说,服务已经恢复,虚拟助理如所预期的那样工作.
自动翻译自官方事件更新。
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.
