Sumo Logic Outage History

The incident affected Cloud Collection for cloudSyslog Source, causing latency in data retrieval and degraded ingestion across multiple regions (US2, EU, FED, AU, JP, IN, US1, DE, KR, CA). The outage began at 12:50 PM UTC and was resolved by 6:30 PM UTC, lasting about 5 hours and 40 minutes. Affected users may have experienced delays in data availability during the window. The provider posted two updates during the incident describing the latency issue and ongoing investigation.

Sumo Logic reported a degraded issue in the CSE Processing Pipeline for North America 1 (US1), causing latency in processing and displaying security data. The incident began on 8:40 AM UTC and was resolved by 10:05 AM UTC, lasting about 1 hour and 25 minutes. The degradation appeared to affect only the US1 region's CSE Processing Pipeline, with users experiencing delays in security data availability.

Sumo Logic experienced latency in Tracing Collection, causing delays in processing and displaying tracing data. The issue affected the Tracing Collection component in North America 1 (US1), resulting in degraded tracing visibility for users.

The incident began at 5:20 PM UTC and was resolved by 6:15 PM UTC, lasting about 55 minutes. The status page published two updates during the incident to communicate the degradation and resolution.

Sumo Logic conducted a scheduled maintenance window in the North America 2 (US2) region, affecting four components: Logs Collection / North America 2 (US2), Automation Service / North America 2 (US2), CSOAR User Interface / North America 2 (US2), and Metrics Collection / North America 2 (US2). During the window, these functions were unavailable or experienced processing delays, leading to delays in data collection, collector registration, Cloud SOAR Automation features, and the display of metrics data. No data loss is expected and no user action is required after the window.

An outage affected Sumo Logic's Tracing Collection in Australia, causing latency in processing and displaying tracing data for about 35 minutes. The AU component moved to a degraded state at 9:45 AM UTC and was restored at 10:20 AM UTC after the investigation concluded. The incident was confined to the Tracing Collection / Australia (AU) component, with no evidence of a wider platform impact. Sumo Logic communicated the issue via status updates, noting the ongoing investigation and later confirming restoration.

Sumo Logic conducted a scheduled maintenance window from 4:00 AM UTC to 7:00 AM UTC, during which several components were placed in maintenance. Affected components included Logs Collection / America Federal (FED) and Metrics Collection / America Federal (FED), plus Metrics Searches / North America 1 (US1), Automation Service / North America 1 (US1), CSOAR User Interface / North America 1 (US1), and Metrics Collection / North America 1 (US1). During this period users could experience delays in data collection and collector registration, as well as delays in processing and displaying metrics data. No data loss is expected and no user action is required after the window. Disruptions to certain Cloud SOAR Automation functionality were possible.

Sumo Logic experienced a brief outage in the Metrics Collection component affecting the Australia (AU) region, causing latency in processing and displaying metrics data. The incident began at 9:55 AM UTC and was resolved by 10:45 AM UTC, lasting about 50 minutes. This outage impacted metrics ingestion and display for users relying on the AU region.

An issue with Tracing Collection caused latency in processing and displaying tracing data for two regions: Europe 2 (DE) and Australia (AU). The incident began at 8:55 AM UTC and was resolved by 9:35 AM UTC, lasting about 40 minutes. Sumo Logic issued two status updates during the event, noting latency in tracing data across the affected components: Tracing Collection / Europe 2 (DE) and Tracing Collection / Australia (AU). The problem was regional, with other regions unaffected, and services returned to normal once the issue was resolved.

Sumo Logic experienced degraded performance in Data Indexing for the North America 2 (US2) region, causing latency in processing and displaying log data. The issue began on Jan 30, 2026 6:35 AM UTC and was resolved by 7:05 AM UTC. The service issued two status updates during the incident as the Data Indexing component transitioned from degraded to healthy. The impact was localized to the US2 data indexing component and lasted about 30 minutes.

Sumo Logic experienced a brief degradation in Data Indexing for the North America 1 (US1) component, causing latency in processing and displaying log data. The incident began at Jan 23, 2026 10:20 AM UTC and was resolved by Jan 23, 2026 10:45 AM UTC, lasting about 25 minutes and affecting users relying on real-time log indexing in US1.

The provider issued two status updates during the incident. The first noted a problem with Data Indexing, and the second confirmed resolution and the US1 component returning to normal.