Histórico de interrupções do Glia

1. 1 Gwengolo 2026 da 16:44 UTCinvestigating

   Estamos trabalhando ativamente com nosso provedor de telefonia para resolver um problema que afeta uma pequena porcentagem de interações vocais. Todos os canais digitais permanecem totalmente operacionais e não afetados.

2. 1 Gwengolo 2026 da 16:51 UTCidentified

   A questão foi identificada e estamos a trabalhar com urgência com o nosso fornecedor na resolução da questão.

3. 1 Gwengolo 2026 da 17:17 UTCidentified

   O vendedor identificou o problema na sua extremidade. Continuamos a trabalhar com eles.

4. 1 Gwengolo 2026 da 17:35 UTCmonitoring

   Uma correção foi implementada do nosso provedor e estamos monitorando o sistema como ele recupera. Continuamos a acompanhar a questão.

5. 1 Gwengolo 2026 da 17:38 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 31 Eost 2026 da 17:29 UTCinvestigating

   Estamos actualmente a investigar uma questão que afecta o desempenho dos compromissos. Estamos a trabalhar para resolver esta questão. Vamos compartilhar informações atualizadas aqui o mais rápido possível.

2. 31 Eost 2026 da 17:38 UTCmonitoring

   Nós implementamos uma correção e estamos monitorando o sistema à medida que ele se recupera. Continuamos a acompanhar a questão.

3. 31 Eost 2026 da 17:43 UTCresolved

   O incidente foi resolvido, nossa telemetria e monitoramento mostram que todas as características são totalmente funcionais.

Traduzido automaticamente da atualização oficial do incidente.

1. 28 Eost 2026 da 21:12 UTCinvestigating

   Estamos a investigar uma potencial degradação do desempenho do Glia. Estamos a trabalhar para resolver esta questão.

2. 28 Eost 2026 da 22:26 UTCinvestigating

   A equipe continua investigando a degradação do desempenho atual com alta prioridade. Nossos achados indicam que isso está impactando a disponibilidade do operador e o relato preciso dos estados de engajamento.

3. 28 Eost 2026 da 22:39 UTCmonitoring

   Nós implementamos uma correção e estamos monitorando o sistema à medida que ele se recupera. Continuamos a acompanhar a questão.

4. 28 Eost 2026 da 22:50 UTCresolved

   O incidente foi totalmente resolvido com todas as instâncias totalmente funcionais e funcionando como esperado.

Traduzido automaticamente da atualização oficial do incidente.

1. 3 Eost 2026 da 21:58 UTCinvestigating

   Nosso provedor de serviços relatou interrupção de serviço afetando o Assistente Virtual. Estamos nos comunicando com nosso provedor de serviços e monitorando de perto o incidente e seus desenvolvimentos para corrigi-lo. Obrigado pela vossa paciência.

2. 3 Eost 2026 da 22:28 UTCmonitoring

   Continuamos a comunicar com o nosso prestador de serviços para monitorizar de perto o incidente e acompanhar os seus desenvolvimentos para o corrigir.

3. 3 Eost 2026 da 22:54 UTCresolved

   Nosso provedor de serviços relatou que o serviço foi restaurado e o Assistente Virtual funciona como esperado.

Traduzido automaticamente da atualização oficial do incidente.

1. 24 Mezheven 2026 da 17:10 UTCinvestigating

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

2. 24 Mezheven 2026 da 17:11 UTCidentified

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

3. 24 Mezheven 2026 da 17:11 UTCmonitoring

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

4. 24 Mezheven 2026 da 17:22 UTCresolved

   This incident has been resolved.

1. 10 Mezheven 2026 da 15: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. 10 Mezheven 2026 da 16: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. 10 Mezheven 2026 da 16: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. 10 Mezheven 2026 da 17: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. 8 Mae 2026 da 01: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. 8 Mae 2026 da 02:05 UTCmonitoring

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

3. 8 Mae 2026 da 02:12 UTCresolved

   Glia is fully operational and the incident is resolved.

1. 8 Mae 2026 da 00: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. 8 Mae 2026 da 01:15 UTCmonitoring

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

3. 8 Mae 2026 da 01:47 UTCresolved

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

1. 19 Genver 2026 da 13:17 UTCinvestigating

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

2. 19 Genver 2026 da 13:28 UTCidentified

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

3. 19 Genver 2026 da 13:35 UTCmonitoring

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

4. 19 Genver 2026 da 13:43 UTCresolved

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

1. 11 Kerzu 2025 da 13: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. 11 Kerzu 2025 da 15:08 UTCinvestigating

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

3. 11 Kerzu 2025 da 18:14 UTCresolved

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

1. 3 Kerzu 2025 da 16: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. 3 Kerzu 2025 da 16:55 UTCresolved

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

1. 3 Du 2025 da 18:12 UTCinvestigating

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

2. 3 Du 2025 da 19:09 UTCmonitoring

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

3. 3 Du 2025 da 19:29 UTCmonitoring

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

4. 3 Du 2025 da 19:44 UTCresolved

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

1. 21 Here 2025 da 14: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. 21 Here 2025 da 14:48 UTCresolved

   This incident has been resolved.

1. 20 Here 2025 da 23: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. 21 Here 2025 da 06:51 UTCresolved

   This incident has been resolved.

1. 20 Here 2025 da 22: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. 20 Here 2025 da 22:38 UTCmonitoring

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

3. 20 Here 2025 da 22:57 UTCresolved

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

1. 20 Here 2025 da 16: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. 20 Here 2025 da 16:38 UTCinvestigating

   We are continuing to investigate this issue.

3. 20 Here 2025 da 17: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. 20 Here 2025 da 17: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. 20 Here 2025 da 18: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. 20 Here 2025 da 18: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. 20 Here 2025 da 19: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. 20 Here 2025 da 19: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. 20 Here 2025 da 19: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. 20 Here 2025 da 20: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. 20 Here 2025 da 20:40 UTCmonitoring

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

12. 20 Here 2025 da 21:08 UTCresolved

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

1. 20 Here 2025 da 14: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. 20 Here 2025 da 15: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. 20 Here 2025 da 17: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. 20 Here 2025 da 17: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. 20 Here 2025 da 18: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. 20 Here 2025 da 18: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. 20 Here 2025 da 19: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. 20 Here 2025 da 19: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. 20 Here 2025 da 20:06 UTCmonitoring

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

10. 20 Here 2025 da 20:42 UTCresolved

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

1. 20 Here 2025 da 14: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. 20 Here 2025 da 14: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. 20 Here 2025 da 15: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. 20 Here 2025 da 17: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. 20 Here 2025 da 17: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. 20 Here 2025 da 18: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. 20 Here 2025 da 18: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. 20 Here 2025 da 18:56 UTCmonitoring

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

9. 20 Here 2025 da 19:45 UTCresolved

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

1. 20 Here 2025 da 13: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. 20 Here 2025 da 13:37 UTCinvestigating

   We are continuing to investigate this issue.

3. 20 Here 2025 da 14: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. 20 Here 2025 da 15: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. 20 Here 2025 da 17: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. 20 Here 2025 da 18: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. 20 Here 2025 da 19: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. 20 Here 2025 da 19: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. 20 Here 2025 da 20: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. 20 Here 2025 da 20: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. 20 Here 2025 da 21: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. 20 Here 2025 da 22: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. 20 Here 2025 da 23: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. 20 Here 2025 da 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. 20 Here 2025 da 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. 20 Here 2025 da 15: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. 20 Here 2025 da 16: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. 20 Here 2025 da 17: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. 20 Here 2025 da 18: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. 20 Here 2025 da 18: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. 20 Here 2025 da 19: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. 20 Here 2025 da 19: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. 20 Here 2025 da 20: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. 20 Here 2025 da 20: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. 20 Here 2025 da 21:42 UTCresolved

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