Glia Outage History

Glia is up right now

Glia had 33 outages in the last 2 years totaling 7h 11m of downtime — averaging 1.4 incidents per month.

There were 33 Glia outages since May 30, 2024 totaling 7h 11m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.glia.com

Minor November 29, 2024

Elevated latency on Engagement Explorer

Detected by Pingoru
Nov 29, 2024, 04:28 PM UTC
Resolved
Nov 29, 2024, 07:58 PM UTC
Duration
3h 29m
Timeline · 4 updates
  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 →

Minor October 21, 2024

Degradation of service for digital engagements

Detected by Pingoru
Oct 21, 2024, 01:45 PM UTC
Resolved
Oct 21, 2024, 02:08 PM UTC
Duration
23m
Timeline · 4 updates
  1. investigating Oct 21, 2024, 01:45 PM UTC

    We are currently investigating a potential degradation of service affecting digital engagements only. Phone engagements remain unaffected.

  2. investigating Oct 21, 2024, 01:57 PM UTC

    Update - Service disruption on the Glia Platform is affecting digital engagements. Phone engagements remain unaffected.

  3. monitoring Oct 21, 2024, 02:04 PM UTC

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

  4. resolved Oct 21, 2024, 02:08 PM UTC

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

Read the full incident report →

Notice September 20, 2024

Service disruption of Glia Platform affecting Operating Statuses reporting

Detected by Pingoru
Sep 20, 2024, 10:32 AM UTC
Resolved
Sep 20, 2024, 11:47 AM UTC
Duration
1h 15m
Timeline · 3 updates
  1. identified Sep 20, 2024, 10:32 AM UTC

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

  2. monitoring Sep 20, 2024, 11:09 AM UTC

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

  3. resolved Sep 20, 2024, 11:47 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 23, 2024

Elevated number of errors in our telemetry affecting the ability of Agents to interact with Customers

Detected by Pingoru
Aug 23, 2024, 01:17 PM UTC
Resolved
Aug 23, 2024, 01:32 PM UTC
Duration
15m
Affected: Communications
Timeline · 3 updates
  1. investigating Aug 23, 2024, 01:17 PM UTC

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

  2. monitoring Aug 23, 2024, 01:27 PM UTC

    We have identified and apply a fix. Agents are able to interact with customers.

  3. resolved Aug 23, 2024, 01:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 21, 2024

Degradation of service affecting some visitors to not be able to connect with Operators.

Detected by Pingoru
Aug 21, 2024, 07:33 PM UTC
Resolved
Aug 21, 2024, 08:00 PM UTC
Duration
27m
Affected: Overall System Status Americas
Timeline · 5 updates
  1. investigating Aug 21, 2024, 07:43 PM UTC

    We are currently investigating this issue.

  2. investigating Aug 21, 2024, 07:44 PM UTC

    We are continuing to investigate this issue.

  3. identified Aug 21, 2024, 07:48 PM UTC

    The issue has been identified and we are applying configuration changes.

  4. monitoring Aug 21, 2024, 07:51 PM UTC

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

  5. resolved Aug 21, 2024, 08:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 3, 2024

Data in Engagement Explorer may be delayed for some users

Detected by Pingoru
Jul 03, 2024, 01:55 AM UTC
Resolved
Jul 03, 2024, 02:57 AM UTC
Duration
1h 1m
Affected: Real-time Analytics
Timeline · 3 updates
  1. identified Jul 03, 2024, 01:55 AM UTC

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

  2. monitoring Jul 03, 2024, 02:41 AM UTC

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

  3. resolved Jul 03, 2024, 02:57 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 3, 2024

Intermittent errors with Bot Engagements

Detected by Pingoru
Jul 03, 2024, 12:39 AM UTC
Resolved
Jul 03, 2024, 12:44 AM UTC
Duration
4m
Affected: Overall System Status AmericasGlia Virtual Assistant (GVA)
Timeline · 4 updates
  1. investigating Jul 03, 2024, 12:23 AM UTC

    We are currently investigating this issue.

  2. investigating Jul 03, 2024, 12:24 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Jul 03, 2024, 12:39 AM UTC

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

  4. resolved Jul 03, 2024, 01:50 AM UTC

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

Read the full incident report →

Major May 30, 2024

Elevated rate of errors for Glia affecting engagements

Detected by Pingoru
May 30, 2024, 04:21 PM UTC
Resolved
May 30, 2024, 04:35 PM UTC
Duration
13m
Affected: Overall System Status Americas
Timeline · 4 updates
  1. investigating May 30, 2024, 04:21 PM UTC

    We are experiencing intermittent failures to a percentage of our Engagements. Affected Engagements are unable to connect. We are working to resolve this issue.

  2. investigating May 30, 2024, 04:32 PM UTC

    We are continuing to investigate this issue.

  3. monitoring May 30, 2024, 04:33 PM UTC

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

  4. resolved May 30, 2024, 04:35 PM UTC

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

Read the full incident report →