Glia Outage History

Glia is up right now

Pingoru has recorded 50 incidents for Glia: 12 in the last 12 months and 4 in the last 90 days.

Source: status.glia.com

50incidents recorded
12last 12 months
4last 90 days
56 minutestypical duration
Incidents per month
024AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Glia in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202622 of 744 (0%)
June 202622 of 720 (0%)
July 202600 of 744 (0%)
August 202633 of 744 (0%)
September 202611 of 720 (0%)
October 202600 of 526 (0%)

Incidents, newest first

Minor September 1, 2026 Potential degraded Glia performance 54m Communications

Started Sep 01, 2026, 04:44 PM UTC· resolved Sep 01, 2026, 05:38 PM UTC

  1. investigating Sep 01, 2026, 04:44 PM UTC

    We are actively working with our telephony provider to resolve an issue affecting a small percentage of voice interactions. All digital channels remain fully operational and unaffected.

  2. identified Sep 01, 2026, 04:51 PM UTC

    The issue has been identified and we are urgently working with our provider in resolving the issue.

  3. identified Sep 01, 2026, 05:17 PM UTC

    The vendor has identified the issue on their end. We continue working with them.

  4. monitoring Sep 01, 2026, 05:35 PM UTC

    A fix has been implemented from our provider and we are monitoring the system as it recovers. We are continuing to monitor the issue.

  5. resolved Sep 01, 2026, 05:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 31, 2026 Service disruption of Glia Platform affecting engagements 13m Overall System Status Americas, Communications, CoBrowsing, Glia Virtual Assistant (GVA)

Started Aug 31, 2026, 05:29 PM UTC· resolved Aug 31, 2026, 05:43 PM UTC

  1. investigating Aug 31, 2026, 05:29 PM UTC

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

  2. monitoring Aug 31, 2026, 05:38 PM UTC

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

  3. resolved Aug 31, 2026, 05:43 PM UTC

    The incident has been resolved, our telemetry and monitoring shows that all features are fully functional.

Read the full incident report →

Minor August 3, 2026 [Some GVA users] Service provider reporting service disruption affecting Virtual Assistant 55m Glia Virtual Assistant (GVA)

Started Aug 03, 2026, 09:58 PM UTC· resolved Aug 03, 2026, 10:54 PM UTC

  1. investigating Aug 03, 2026, 09:58 PM UTC

    Our service provider has reported service disruption affecting Virtual Assistant. We are communicating with our service provider and closely monitoring the incident and their developments to fix it. Thank you for your patience.

  2. monitoring Aug 03, 2026, 10:28 PM UTC

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

  3. resolved Aug 03, 2026, 10:54 PM UTC

    Our service provider has reported that service has been restored and Virtual Assistant works as expected.

Read the full incident report →

Notice June 24, 2026 GVA Downtime 12m Glia Virtual Assistant (GVA)

Started Jun 24, 2026, 05:09 PM UTC· resolved Jun 24, 2026, 05:22 PM UTC

  1. investigating Jun 24, 2026, 05:09 PM UTC

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

  2. investigating Jun 24, 2026, 05:10 PM UTC

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

  3. identified Jun 24, 2026, 05:11 PM UTC

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

  4. monitoring Jun 24, 2026, 05:11 PM UTC

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

  5. resolved Jun 24, 2026, 05:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 10, 2026 [Some GVA Users] Elevated rate of errors for Auth GVA 1h 43m Glia Virtual Assistant (GVA)

Started Jun 10, 2026, 03:37 PM UTC· resolved Jun 10, 2026, 05:20 PM UTC

  1. investigating Jun 10, 2026, 03:37 PM UTC

    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. identified Jun 10, 2026, 04:06 PM UTC

    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. monitoring Jun 10, 2026, 04:49 PM UTC

    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. resolved Jun 10, 2026, 05:20 PM UTC

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

Read the full incident report →

Notice May 8, 2026 Elevated rate of errors for Glia affecting reporting 52m

Started May 08, 2026, 01:20 AM UTC· resolved May 08, 2026, 02:12 AM UTC

  1. identified May 08, 2026, 01:20 AM UTC

    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. monitoring May 08, 2026, 02:05 AM UTC

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

  3. resolved May 08, 2026, 02:12 AM UTC

    Glia is fully operational and the incident is resolved.

Read the full incident report →

Major May 8, 2026 Service provider reporting service disruption affecting Glia 1h 9m

Started May 08, 2026, 12:37 AM UTC· resolved May 08, 2026, 01:47 AM UTC

  1. identified May 08, 2026, 12:37 AM UTC

    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. monitoring May 08, 2026, 01:15 AM UTC

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

  3. resolved May 08, 2026, 01:47 AM UTC

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

Read the full incident report →

Notice January 19, 2026 Partial degradation of service 25m

Started Jan 19, 2026, 01:17 PM UTC· resolved Jan 19, 2026, 01:43 PM UTC

  1. investigating Jan 19, 2026, 01:17 PM UTC

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

  2. identified Jan 19, 2026, 01:28 PM UTC

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

  3. monitoring Jan 19, 2026, 01:35 PM UTC

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

  4. resolved Jan 19, 2026, 01:43 PM UTC

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

Read the full incident report →

Notice December 11, 2025 Partial degradation of outbound calls 1h 42m

Started Dec 11, 2025, 01:47 PM UTC· resolved Dec 11, 2025, 03:30 PM UTC

  1. investigating Dec 11, 2025, 01:47 PM UTC

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

  2. investigating Dec 11, 2025, 03:08 PM UTC

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

  3. resolved Dec 11, 2025, 06:14 PM UTC

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

Read the full incident report →

Notice December 3, 2025 Elevated number of errors affecting a small number of Phone GVA interactions 5m

Started Dec 03, 2025, 04:49 PM UTC· resolved Dec 03, 2025, 04:55 PM UTC

  1. monitoring Dec 03, 2025, 04:49 PM UTC

    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. resolved Dec 03, 2025, 04:55 PM UTC

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

Read the full incident report →

Minor November 3, 2025 Service disruption of Glia Platform affecting Cortex AI 1h 31m Glia Virtual Assistant (GVA)

Started Nov 03, 2025, 06:12 PM UTC· resolved Nov 03, 2025, 07:44 PM UTC

  1. investigating Nov 03, 2025, 06:12 PM UTC

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

  2. monitoring Nov 03, 2025, 07:09 PM UTC

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

  3. monitoring Nov 03, 2025, 07:29 PM UTC

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

  4. resolved Nov 03, 2025, 07:44 PM UTC

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

Read the full incident report →

Minor October 21, 2025 Elevated number of errors in our telemetry impacting Cortex AI features 5m

Started Oct 21, 2025, 02:42 PM UTC· resolved Oct 21, 2025, 02:48 PM UTC

  1. investigating Oct 21, 2025, 02:42 PM UTC

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

  2. resolved Oct 21, 2025, 02:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 20, 2025 Service disruption of Glia Platform affecting Insights 7h 43m

Started Oct 20, 2025, 11:08 PM UTC· resolved Oct 21, 2025, 06:51 AM UTC

  1. monitoring Oct 20, 2025, 11:33 PM UTC

    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. resolved Oct 21, 2025, 06:51 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 20, 2025 Infrastructure Service Provider Reporting Service Disruption Affecting Glia Engagement Routing 21m Overall System Status Americas, Overall System Status EU

Started Oct 20, 2025, 10:35 PM UTC· resolved Oct 20, 2025, 10:57 PM UTC

  1. identified Oct 20, 2025, 10:35 PM UTC

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

  2. monitoring Oct 20, 2025, 10:38 PM UTC

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

  3. resolved Oct 20, 2025, 10:57 PM UTC

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

Read the full incident report →

Minor October 20, 2025 Infrastructure service provider reporting service disruption affecting Glia Engagement Routing 4h 33m Overall System Status Americas

Started Oct 20, 2025, 04:35 PM UTC· resolved Oct 20, 2025, 09:08 PM UTC

  1. investigating Oct 20, 2025, 04:35 PM UTC

    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. investigating Oct 20, 2025, 04:38 PM UTC

    We are continuing to investigate this issue.

  3. investigating Oct 20, 2025, 05:01 PM UTC

    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. investigating Oct 20, 2025, 05:35 PM UTC

    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. investigating Oct 20, 2025, 06:09 PM UTC

    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. investigating Oct 20, 2025, 06:31 PM UTC

    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. investigating Oct 20, 2025, 07:03 PM UTC

    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. investigating Oct 20, 2025, 07:35 PM UTC

    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. investigating Oct 20, 2025, 07:51 PM UTC

    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. investigating Oct 20, 2025, 08:37 PM UTC

    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. monitoring Oct 20, 2025, 08:40 PM UTC

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

  12. resolved Oct 20, 2025, 09:08 PM UTC

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

Read the full incident report →

Minor October 20, 2025 Phone Service Provider reporting service disruption affecting Glia 6h 21m Communications

Started Oct 20, 2025, 02:20 PM UTC· resolved Oct 20, 2025, 08:42 PM UTC

  1. investigating Oct 20, 2025, 02:20 PM UTC

    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. identified Oct 20, 2025, 02:28 PM UTC

    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. identified Oct 20, 2025, 03:30 PM UTC

    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.

  4. identified Oct 20, 2025, 05:00 PM UTC

    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. identified Oct 20, 2025, 05:35 PM UTC

    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. identified Oct 20, 2025, 06:09 PM UTC

    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. identified Oct 20, 2025, 06:32 PM UTC

    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. identified Oct 20, 2025, 07:03 PM UTC

    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. identified Oct 20, 2025, 07:35 PM UTC

    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. monitoring Oct 20, 2025, 08:06 PM UTC

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

  11. resolved Oct 20, 2025, 08:42 PM UTC

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

Read the full incident report →

Minor October 20, 2025 EU: SMS Service Provider reporting service disruption affecting Glia 9h 31m Overall System Status EU

Started Oct 20, 2025, 11:54 AM UTC· resolved Oct 20, 2025, 09:25 PM UTC

  1. identified Oct 20, 2025, 11:54 AM UTC

    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. identified Oct 20, 2025, 11:58 AM UTC

    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. identified Oct 20, 2025, 02:45 PM UTC

    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. identified Oct 20, 2025, 03:28 PM UTC

    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. identified Oct 20, 2025, 04:59 PM UTC

    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. identified Oct 20, 2025, 05:33 PM UTC

    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).

  7. identified Oct 20, 2025, 06:10 PM UTC

    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).

  8. identified Oct 20, 2025, 06:33 PM UTC

    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).

  9. identified Oct 20, 2025, 07:03 PM UTC

    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).

  10. identified Oct 20, 2025, 07:36 PM UTC

    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).

  11. identified Oct 20, 2025, 08:02 PM UTC

    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).

  12. identified Oct 20, 2025, 08:37 PM UTC

    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).

  13. resolved Oct 20, 2025, 09:42 PM UTC

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

Read the full incident report →

Major October 20, 2025 Infrastructure service provider reporting service disruption affecting Glia 1h 17m

Started Oct 20, 2025, 09:48 AM UTC· resolved Oct 20, 2025, 11:06 AM UTC

  1. identified Oct 20, 2025, 09:48 AM UTC

    The platform provider reported that mitigation steps have been applied. Services are still in recovery at this time.

  2. identified Oct 20, 2025, 10:13 AM UTC

    The platform provider reported that mitigation steps have been applied. Services are still in recovery at this time.

  3. identified Oct 20, 2025, 10:27 AM UTC

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

  4. monitoring Oct 20, 2025, 10:30 AM UTC

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

  5. resolved Oct 20, 2025, 11:14 AM UTC

    Our service provider has reported that the service has been restored, and Glia works as expected.

Read the full incident report →

Minor September 24, 2025 [All GVA users] Potential degraded Virtual Assistant performance 25m Glia Virtual Assistant (GVA)

Started Sep 24, 2025, 04:11 PM UTC· resolved Sep 24, 2025, 04:36 PM UTC

  1. investigating Sep 24, 2025, 04:11 PM UTC

    We are currently investigating a potential degradation of Virtual Assistant performance. We are working to resolve this issue. Thank you for your patience.

  2. monitoring Sep 24, 2025, 04:27 PM UTC

    We have implemented a fix and are monitoring the system as it recovers. Thank you for your patience.

  3. resolved Sep 24, 2025, 04:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 24, 2025 Elevated number of errors in our telemetry for SMS 31m Communications

Started Sep 24, 2025, 03:46 PM UTC· resolved Sep 24, 2025, 04:18 PM UTC

  1. investigating Sep 24, 2025, 03:46 PM UTC

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

  2. investigating Sep 24, 2025, 03:49 PM UTC

    We're currently investigating an issue affecting SMS communications. This incident is limited to SMS messages, and all other services are operating normally. We'll provide another update as soon as we have more information.

  3. monitoring Sep 24, 2025, 04:12 PM UTC

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

  4. resolved Sep 24, 2025, 04:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 24, 2025 [All GVA users] Virtual Assistant service disruption 44m Glia Virtual Assistant (GVA)

Started Aug 24, 2025, 12:48 AM UTC· resolved Aug 24, 2025, 01:32 AM UTC

  1. investigating Aug 24, 2025, 12:48 AM UTC

    We are currently investigating an issue resulting in the Virtual Assistant being unavailable. All other Glia functionalities are working as expected. We are working to resolve this issue. Thank you for your patience.

  2. resolved Aug 24, 2025, 01:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 11, 2025 Delay in Historical Reporting and Statistics 2h 6m

Started Aug 11, 2025, 12:45 PM UTC· resolved Aug 11, 2025, 02:52 PM UTC

  1. investigating Aug 11, 2025, 12:45 PM UTC

    We are currently investigating a delay in the ingestion of analytical data used in our Historical Reporting and Statistics services. All other functionality, including Glia Insights, are fully operational. We are working to solve this issue.

  2. identified Aug 11, 2025, 01:26 PM UTC

    The issue has been identified and we are urgently working on resolving the issue.

  3. identified Aug 11, 2025, 02:19 PM UTC

    Our operations teams continue being focused on resolving this issue.

  4. monitoring Aug 11, 2025, 02:38 PM UTC

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

  5. resolved Aug 11, 2025, 02:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical July 17, 2025 GVA Service is Unavailable 44m Glia Virtual Assistant (GVA)

Started Jul 17, 2025, 10:21 PM UTC· resolved Jul 17, 2025, 11:05 PM UTC

  1. investigating Jul 17, 2025, 10:21 PM UTC

    GVAs are not responding. We are working on this as the highest priority.

  2. identified Jul 17, 2025, 10:36 PM UTC

    The issue has been identified and we are urgently working on resolving the issue.

  3. monitoring Jul 17, 2025, 10:55 PM UTC

    The operations team has implemented a fix and our telemetry shows that the system is working as expected and all GVAs are fully functional

  4. monitoring Jul 17, 2025, 10:55 PM UTC

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

  5. resolved Jul 17, 2025, 11:05 PM UTC

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

Read the full incident report →

Major July 15, 2025 Service disruption of Glia Platform affecting several Hub features 3h 46m

Started Jul 15, 2025, 01:53 PM UTC· resolved Jul 15, 2025, 05:39 PM UTC

  1. identified Jul 15, 2025, 01:53 PM UTC

    The issue has been identified and we are urgently working on resolving the issue.

  2. monitoring Jul 15, 2025, 02:52 PM UTC

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

  3. resolved Jul 15, 2025, 05:39 PM UTC

    All Glia systems are operational and services are back and running.

Read the full incident report →

Notice June 12, 2025 Google Dialog Flow Outage 1h 36m

Started Jun 12, 2025, 07:08 PM UTC· resolved Jun 12, 2025, 08:45 PM UTC

  1. monitoring Jun 12, 2025, 07:08 PM UTC

    There is an elevated number of errors from Google Dialog Flow affecting integrations connecting to these services. All Glia services, including GVAs are fully functional. We recommend that customers with these integrations monitor and contact Dialog Flow.

  2. resolved Jun 13, 2025, 07:30 AM UTC

    Our service provider has reported that service has been restored, our telemetry and monitoring shows all Glia services, including GVAs are fully functional.

Read the full incident report →