Sumo Logic outage history

Users in the Europe 1 (EU) region experienced degraded performance in Sumo Logic Cloud SIEM Processing, with latency in processing and displaying security data. The issue began at 5:45 PM UTC and persisted for about fifty minutes, affecting security dashboards and data visibility. The source was identified at 6:20 PM UTC and a fix was implemented by 6:25 PM UTC. Service monitoring confirmed recovery by 6:35 PM UTC.

Users in North America 2 (US2) experienced latency in processing and displaying logs, metrics, and tracing data. The problem affected the US2 Logs Collection, Metrics Collection, and Tracing Collection components, causing delays in data processing and visible dashboards for monitoring and analytics. Impact began at 9:10 PM UTC and continued while the issue was being investigated. Sumo Logic confirmed the issue, identified the source, and rolled out a fix while actively monitoring results. By 10:05 PM UTC, Logs Collection, Metrics Collection, and Tracing Collection in US2 had returned to normal operation, and latency concerns subsided.

Users relying on Sumo Logic Logs Alerting and Metrics Alerting in the Europe 2 (DE) region experienced latency and delays in data display starting at 10:01 AM UTC. The issue affected the Europe 2 (DE) Logs Alerting and Metrics Alerting components, causing slower alert generation and delayed visibility in dashboards. Sumo Logic identified the source of the problem and began implementing a fix, with the affected components returning to normal by 11:10 AM UTC. The incident appeared regional to Europe 2 (DE) without wider impact.

Sumo Logic experienced latency in processing and displaying log data in North America 2 (US2) starting at 8:20 AM UTC due to a Data Indexing issue. The problem reduced the visibility of logs and dashboards for users in this region.

A fix was implemented by 8:30 AM UTC and the team kept monitoring as the incident expanded to Cloud SIEM Processing. By 9:25 AM UTC both Data Indexing and Cloud SIEM Processing had returned to up, indicating the issue had been resolved for US2.

Users in the America Federal (FED) region relying on Logs Alerting experienced notification gaps during a brief incident on Sumo Logic. The issue began at 8:05 PM UTC and affected the Logs Alerting component in FED; a status update at 8:20 PM UTC indicated the source was identified and a fix was in progress. The incident did not indicate a global outage but impacted regional alerting for FED. By 8:25 PM UTC the FED Logs Alerting component had returned to normal, restoring notifications.

Sumo Logic ran staged maintenance affecting the data collection pipelines in North America. Beginning at 5:00 AM UTC, North America 1 (US1) Logs Collection, Metrics Collection, and Tracing Collection entered maintenance, which likely paused data ingestion in US1 during that window. By 6:05 AM UTC, US1 components were back online, while North America 2 (US2) collection components moved into maintenance. The US2 maintenance continued until 7:00 AM UTC, after which US2 components returned to operation. All collection services were restored by 7:00 AM UTC.

The North America 2 (US2) Metrics Collection pipeline began experiencing latency in processing and displaying metrics data at 5:10 PM UTC due to a networking issue in Microsoft Azure's West US region. This regional disruption affected dashboards and metrics visibility for users monitoring Azure metrics via Sumo Logic, with data updates appearing delayed.

At 6:55 PM UTC, Microsoft Azure identified and rolled back a change tied to the networking problem, and signs of recovery followed as processing latency started to return to normal. The US2 Metrics Collection returned to normal operation by 7:15 PM UTC.

Sumo Logic experienced latency in the CSE Processing Pipeline for North America 1 (US1), causing delays in processing and displaying security data. The issue began at 9:25 AM UTC and impacted visibility across security dashboards for users relying on real-time data. A fix was implemented by 10:10 AM UTC and engineers monitored the results, with the pipeline returning to normal by 11:45 AM UTC.

Users in North America 1 (US1) relying on Metrics Searches may have encountered errors when executing metric queries. The incident began at 3:20 AM UTC and was resolved by 5:35 AM UTC, lasting a little over two hours. Sumo Logic's status page indicated the team was investigating reports of problems with Metrics Searches; the North America 1 (US1) Metrics Searches component was listed as degraded before returning to normal. The disruption appeared limited to the US1 region, with no broader regional impact reported.

Sumo Logic reported a problem with the CSE Processing Pipeline in Europe 1 (EU), causing latency in processing and displaying security data. The issue began at 6:55 AM UTC and led to degraded performance for users relying on EU data processing. The impact was centered on the Europe 1 (EU) region and affected the CSE Processing Pipeline.