All Systems Operational

Uptime over the past 90 days. View historical uptime.
Overall System Status Americas Operational
90 days ago
100.0 % uptime
Today
Overall System Status EU Operational
90 days ago
100.0 % uptime
Today
Real-time Analytics Operational
Communications Operational
CoBrowsing Operational
Glia Virtual Assistant (GVA) Operational
AWS ec2-us-east-1 Operational
AWS ec2-eu-west-1 Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

EU Failover training Nov 2, 2025 04:00-06:00 UTC

We are testing our failover procedures. Only EU clients are affected.
Posted on Oct 16, 2025 - 12:42 UTC
System Metrics Month Week Day
Pubsub Response
Fetching
Pubsub Response EU
Fetching
API Response US
Fetching
API Response EU
Fetching
Oct 21, 2025
Elevated number of errors in our telemetry impacting Cortex AI features
Resolved - This incident has been resolved.
Oct 21, 14:48 UTC
Investigating - We are currently investigating an elevated number of errors in our telemetry with Cortex AI. We are working to solve this issue.
Oct 21, 14:42 UTC
Service disruption of Glia Platform affecting Insights
Resolved - This incident has been resolved.
Oct 21, 06:51 UTC
Monitoring - 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.
Oct 20, 23:08 UTC
Oct 20, 2025
Service disruption of Glia Platform affecting Insights
Resolved - 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.
Oct 20, 23:08 UTC
Update - 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).
Oct 20, 22:29 UTC
Update - 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).
Oct 20, 21:38 UTC
Update - 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).
Oct 20, 20:37 UTC
Update - 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).
Oct 20, 20:02 UTC
Update - 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).
Oct 20, 19:36 UTC
Update - 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).
Oct 20, 19:03 UTC
Update - 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).
Oct 20, 18:33 UTC
Update - 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).
Oct 20, 18:10 UTC
Update - 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).
Oct 20, 17:34 UTC
Update - 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).
Oct 20, 17:00 UTC
Investigating - We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status).
Oct 20, 15:29 UTC
Identified - We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status).
Oct 20, 14:45 UTC
Update - We are continuing to investigate this issue.
Oct 20, 13:37 UTC
Investigating - 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.
Oct 20, 13:36 UTC
Infrastructure Service Provider Reporting Service Disruption Affecting Glia Engagement Routing
Resolved - The incident has been fully resolved with all instances fully functional and performing as expected.
Oct 20, 22:57 UTC
Monitoring - We have implemented a fix and are monitoring the system as it recovers. We are continuing to monitor the issue.
Oct 20, 22:38 UTC
Identified - The system is recovering. Our engineering team is working on clearing out stuck engagements. Our expected time to completion is 20 min.
Oct 20, 22:35 UTC
EU: SMS Service Provider reporting service disruption affecting Glia
Resolved - Our service provider has reported that service has been restored, telemetry and monitoring shows that Glia SMS Services work as expected.
Oct 20, 21:25 UTC
Update - 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).
Oct 20, 20:37 UTC
Update - 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).
Oct 20, 20:02 UTC
Update - 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).
Oct 20, 19:36 UTC
Update - 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).
Oct 20, 19:03 UTC
Update - 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).
Oct 20, 18:33 UTC
Update - 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).
Oct 20, 18:10 UTC
Update - 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).
Oct 20, 17:33 UTC
Update - 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).
Oct 20, 16:59 UTC
Update - We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status).
Oct 20, 15:28 UTC
Update - We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status).
Oct 20, 14:45 UTC
Update - 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.
Oct 20, 11:58 UTC
Identified - 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.
Oct 20, 11:54 UTC
Infrastructure service provider reporting service disruption affecting Glia Engagement Routing
Resolved - Our service provider has reported that service has been restored, telemetry and monitoring shows that Glia Engagement Routing works as expected.
Oct 20, 21:08 UTC
Monitoring - We continue to communicate with our service provider to monitor the incident closely and follow their developments to fix it.
Oct 20, 20:40 UTC
Update - 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).
Oct 20, 20:37 UTC
Update - 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).
Oct 20, 19:51 UTC
Update - 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).
Oct 20, 19:35 UTC
Update - 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).
Oct 20, 19:03 UTC
Update - 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).
Oct 20, 18:31 UTC
Update - 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).
Oct 20, 18:09 UTC
Update - 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).
Oct 20, 17:35 UTC
Update - 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).
Oct 20, 17:01 UTC
Update - We are continuing to investigate this issue.
Oct 20, 16:38 UTC
Investigating - We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status).
Oct 20, 16:35 UTC
Phone Service Provider reporting service disruption affecting Glia
Resolved - Our service provider has reported that service has been restored, telemetry and monitoring shows that Glia Phone services works as expected.
Oct 20, 20:42 UTC
Monitoring - We continue to communicate with our service provider to monitor the incident closely and follow their developments to fix it.
Oct 20, 20:06 UTC
Update - 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).
Oct 20, 19:35 UTC
Update - 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).
Oct 20, 19:03 UTC
Update - 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).
Oct 20, 18:32 UTC
Update - 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).
Oct 20, 18:09 UTC
Update - 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).
Oct 20, 17:35 UTC
Update - 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).
Oct 20, 17:00 UTC
Update - 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.
Oct 20, 15:30 UTC
Identified - 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.
Oct 20, 14:28 UTC
Investigating - 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.
Oct 20, 14:20 UTC
Service disruption of Glia Platform affecting Cortex AI
Resolved - Our service provider has reported that service has been restored, telemetry and monitoring shows that Cortex AI services works as expected.
Oct 20, 19:45 UTC
Monitoring - We continue to communicate with our service provider to monitor the incident closely and follow their developments to fix it.
Oct 20, 18:56 UTC
Update - 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).
Oct 20, 18:32 UTC
Update - 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).
Oct 20, 18:10 UTC
Update - 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).
Oct 20, 17:34 UTC
Update - 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).
Oct 20, 17:00 UTC
Investigating - We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status).
Oct 20, 15:29 UTC
Identified - We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status).
Oct 20, 14:46 UTC
Investigating - 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.
Oct 20, 14:09 UTC
Infrastructure service provider reporting service disruption affecting Glia
Resolved - Our service provider has reported that the service has been restored, and Glia works as expected.
Oct 20, 11:06 UTC
Monitoring - We continue to communicate with our service provider to monitor the incident closely and follow their developments to fix it.
Oct 20, 10:30 UTC
Update - 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.
Oct 20, 10:27 UTC
Update - The platform provider reported that mitigation steps have been applied. Services are still in recovery at this time.
Oct 20, 10:14 UTC
Identified - The platform provider reported that mitigation steps have been applied. Services are still in recovery at this time.
Oct 20, 10:12 UTC
Oct 19, 2025

No incidents reported.

Oct 18, 2025

No incidents reported.

Oct 17, 2025

No incidents reported.

Oct 16, 2025

No incidents reported.

Oct 15, 2025

No incidents reported.

Oct 14, 2025

No incidents reported.

Oct 13, 2025

No incidents reported.

Oct 12, 2025

No incidents reported.

Oct 11, 2025

No incidents reported.

Oct 10, 2025

No incidents reported.

Oct 9, 2025

No incidents reported.

Oct 8, 2025

No incidents reported.

Oct 7, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage