Historial de interrupciones de Glia

1. September 1, 2026 at 4:44 PM UTCinvestigating

   Trabajamos activamente con nuestro proveedor de telefonía para resolver un problema que afecta a un pequeño porcentaje de interacciones de voz. Todos los canales digitales siguen siendo totalmente operativos y no afectados.

2. September 1, 2026 at 4:51 PM UTCidentified

   La cuestión ha sido identificada y estamos trabajando urgentemente con nuestro proveedor para resolver la cuestión.

3. September 1, 2026 at 5:17 PM UTCidentified

   El proveedor ha identificado la cuestión al final. Continuamos trabajando con ellos.

4. September 1, 2026 at 5:35 PM UTCmonitoring

   Se ha implementado una solución de nuestro proveedor y estamos monitoreando el sistema mientras se recupera. Seguimos vigilando la cuestión.

5. September 1, 2026 at 5:38 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 31, 2026 at 5:29 PM UTCinvestigating

   Actualmente estamos investigando una cuestión que afecta al desempeño de los compromisos. Estamos trabajando para resolver este problema. Compartiremos información actualizada aquí lo antes posible.

2. August 31, 2026 at 5:38 PM UTCmonitoring

   Hemos implementado una solución y estamos monitoreando el sistema mientras se recupera. Seguimos vigilando la cuestión.

3. August 31, 2026 at 5:43 PM UTCresolved

   El incidente ha sido resuelto, nuestra telemetría y monitoreo muestra que todas las características son totalmente funcionales.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 28, 2026 at 9:12 PM UTCinvestigating

   Actualmente estamos investigando una posible degradación del rendimiento de Glia. Estamos trabajando para resolver este problema.

2. August 28, 2026 at 10:26 PM UTCinvestigating

   El equipo sigue investigando la actual degradación del desempeño con alta prioridad. Nuestros hallazgos indican que esto está afectando la disponibilidad del operador y la información exacta de los estados de compromiso.

3. August 28, 2026 at 10:39 PM UTCmonitoring

   Hemos implementado una solución y estamos monitoreando el sistema mientras se recupera. Seguimos vigilando la cuestión.

4. August 28, 2026 at 10:50 PM UTCresolved

   El incidente se ha resuelto plenamente con todos los casos plenamente funcionales y se ha cumplido según lo previsto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 3, 2026 at 9:58 PM UTCinvestigating

   Nuestro proveedor de servicios ha reportado trastornos de servicio que afectan a Virtual Assistant. Nos estamos comunicando con nuestro proveedor de servicios y monitoreamos de cerca el incidente y sus desarrollos para solucionarlo. Gracias por su paciencia.

2. August 3, 2026 at 10:28 PM UTCmonitoring

   Seguimos comunicando con nuestro proveedor de servicios para vigilar el incidente de cerca y seguir sus desarrollos para solucionarlo.

3. August 3, 2026 at 10:54 PM UTCresolved

   Nuestro proveedor de servicios ha informado que el servicio ha sido restaurado y Virtual Assistant funciona como se espera.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 24, 2026 at 5:10 PM UTCinvestigating

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

2. June 24, 2026 at 5:11 PM UTCidentified

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

3. June 24, 2026 at 5:11 PM UTCmonitoring

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

4. June 24, 2026 at 5:22 PM UTCresolved

   This incident has been resolved.

1. June 10, 2026 at 3:37 PM 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. June 10, 2026 at 4:06 PM 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. June 10, 2026 at 4:49 PM 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. June 10, 2026 at 5:20 PM 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. May 8, 2026 at 1:20 AM 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. May 8, 2026 at 2:05 AM UTCmonitoring

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

3. May 8, 2026 at 2:12 AM UTCresolved

   Glia is fully operational and the incident is resolved.

1. May 8, 2026 at 12:37 AM 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. May 8, 2026 at 1:15 AM UTCmonitoring

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

3. May 8, 2026 at 1:47 AM UTCresolved

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

1. January 19, 2026 at 1:17 PM UTCinvestigating

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

2. January 19, 2026 at 1:28 PM UTCidentified

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

3. January 19, 2026 at 1:35 PM UTCmonitoring

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

4. January 19, 2026 at 1:43 PM UTCresolved

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

1. December 11, 2025 at 1:47 PM UTCinvestigating

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

2. December 11, 2025 at 3:08 PM UTCinvestigating

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

3. December 11, 2025 at 6:14 PM UTCresolved

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

1. December 3, 2025 at 4:49 PM 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. December 3, 2025 at 4:55 PM UTCresolved

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

1. November 3, 2025 at 6:12 PM UTCinvestigating

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

2. November 3, 2025 at 7:09 PM UTCmonitoring

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

3. November 3, 2025 at 7:29 PM UTCmonitoring

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

4. November 3, 2025 at 7:44 PM UTCresolved

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

1. October 21, 2025 at 2:42 PM UTCinvestigating

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

2. October 21, 2025 at 2:48 PM UTCresolved

   This incident has been resolved.

1. October 20, 2025 at 11:33 PM 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. October 21, 2025 at 6:51 AM UTCresolved

   This incident has been resolved.

1. October 20, 2025 at 10:35 PM UTCidentified

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

2. October 20, 2025 at 10:38 PM UTCmonitoring

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

3. October 20, 2025 at 10:57 PM UTCresolved

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

1. October 20, 2025 at 4:35 PM 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. October 20, 2025 at 4:38 PM UTCinvestigating

   We are continuing to investigate this issue.

3. October 20, 2025 at 5:01 PM 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. October 20, 2025 at 5:35 PM 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. October 20, 2025 at 6:09 PM 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. October 20, 2025 at 6:31 PM 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. October 20, 2025 at 7:03 PM 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. October 20, 2025 at 7:35 PM 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. October 20, 2025 at 7:51 PM 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. October 20, 2025 at 8:37 PM 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. October 20, 2025 at 8:40 PM UTCmonitoring

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

12. October 20, 2025 at 9:08 PM UTCresolved

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

1. October 20, 2025 at 2:20 PM 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. October 20, 2025 at 3:30 PM 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. October 20, 2025 at 5:00 PM 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. October 20, 2025 at 5:35 PM 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. October 20, 2025 at 6:09 PM 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. October 20, 2025 at 6:32 PM 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. October 20, 2025 at 7:03 PM 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. October 20, 2025 at 7:35 PM 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. October 20, 2025 at 8:06 PM UTCmonitoring

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

10. October 20, 2025 at 8:42 PM UTCresolved

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

1. October 20, 2025 at 2:09 PM 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. October 20, 2025 at 2:46 PM 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. October 20, 2025 at 3:29 PM 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. October 20, 2025 at 5:00 PM 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. October 20, 2025 at 5:34 PM 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. October 20, 2025 at 6:10 PM 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. October 20, 2025 at 6:32 PM 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. October 20, 2025 at 6:56 PM UTCmonitoring

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

9. October 20, 2025 at 7:45 PM UTCresolved

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

1. October 20, 2025 at 1:36 PM 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. October 20, 2025 at 1:37 PM UTCinvestigating

   We are continuing to investigate this issue.

3. October 20, 2025 at 2:45 PM 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. October 20, 2025 at 3:29 PM 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. October 20, 2025 at 5:00 PM 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. October 20, 2025 at 6:33 PM 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. October 20, 2025 at 7:03 PM 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. October 20, 2025 at 7:36 PM 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. October 20, 2025 at 8:02 PM 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. October 20, 2025 at 8:37 PM 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. October 20, 2025 at 9:38 PM 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. October 20, 2025 at 10:29 PM 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. October 20, 2025 at 11:30 PM 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. October 20, 2025 at 11:54 AM 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. October 20, 2025 at 11:58 AM 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. October 20, 2025 at 3:28 PM 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. October 20, 2025 at 4:59 PM 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. October 20, 2025 at 5:33 PM 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. October 20, 2025 at 6:10 PM 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. October 20, 2025 at 6:33 PM 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. October 20, 2025 at 7:03 PM 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. October 20, 2025 at 7:36 PM 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. October 20, 2025 at 8:02 PM 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. October 20, 2025 at 8:37 PM 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. October 20, 2025 at 9:42 PM UTCresolved

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