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 589 (0%)

Incidents, newest first

Minor April 8, 2025 Service provider disruption affecting Quality Analyst feature 2h 2m Glia Virtual Assistant (GVA)

Started Apr 08, 2025, 04:15 PM UTC· resolved Apr 08, 2025, 06:17 PM UTC

  1. investigating Apr 08, 2025, 04:15 PM UTC

    Our service provider has reported service disruption affecting Glia Platform. Affected feature is Quality Analyst. We are closely monitoring the incident and their developments to fix it. All communications are operational and customers can interact with operators.

  2. monitoring Apr 08, 2025, 06:01 PM UTC

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

  3. resolved Apr 08, 2025, 06:17 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 18, 2025 Some visitors are not being able to enqueue and interact with agents. 35m Overall System Status Americas

Started Feb 18, 2025, 06:08 PM UTC· resolved Feb 18, 2025, 06:43 PM UTC

  1. investigating Feb 18, 2025, 06:18 PM UTC

    We are currently investigating this issue.

  2. identified Feb 18, 2025, 06:31 PM UTC

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

  3. monitoring Feb 18, 2025, 06:40 PM UTC

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

  4. resolved Feb 18, 2025, 06:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 13, 2025 Partial service disruption of Glia IVRs 1h 52m Communications

Started Feb 13, 2025, 08:50 PM UTC· resolved Feb 13, 2025, 10:42 PM UTC

  1. investigating Feb 13, 2025, 08:50 PM UTC

    We are currently investigating an issue affecting Glia IVRs. There are known IVR call outages right and our team is working on an update.

  2. identified Feb 13, 2025, 09:34 PM UTC

    The ongoing IVR issue has been identified and our telephony provider is working on a resolution. We are providing alternate options for our clients via our Service Desk affected by the ongoing incident while our telephony provider is working on the fix.

  3. monitoring Feb 13, 2025, 10:27 PM UTC

    A fix has been implemented by our telephony provider and we are monitoring the results.

  4. resolved Feb 13, 2025, 10:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 10, 2025 [Prod EU] Elevated number of errors in our telemetry 2m Overall System Status Americas

Started Jan 10, 2025, 08:45 PM UTC· resolved Jan 10, 2025, 08:47 PM UTC

  1. investigating Jan 10, 2025, 08:45 PM UTC

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

  2. resolved Jan 10, 2025, 08:47 PM UTC

    Glia is fully operational and the incident is resolved.

Read the full incident report →

Minor November 29, 2024 Elevated latency on Engagement Explorer 3h 29m

Started Nov 29, 2024, 04:28 PM UTC· resolved Nov 29, 2024, 07:58 PM UTC

  1. investigating Nov 29, 2024, 04:28 PM UTC

    There is an increase in latency in engagements being displayed in the Engagement Explorer. Our operations team are actively working on resolving this issue.

  2. identified Nov 29, 2024, 04:45 PM UTC

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

  3. monitoring Nov 29, 2024, 07:14 PM UTC

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

  4. resolved Nov 29, 2024, 07:58 PM UTC

    This incident has been resolved.

Read the full incident report →