Sumo Logic Outage History

Sumo Logic reported a brief degradation affecting Logs Alerting in the North America 2 (US2) region. Users may have experienced latency in processing and displaying log data and slower log queries, impacting alerting workflows and real-time visibility. The issue was limited to the Logs Alerting component and did not indicate broader service disruption. The incident began at Sep 23, 2025 11:30 PM UTC and was resolved by Sep 23, 2025 11:45 PM UTC after two status updates on the Sumo Logic status page.

Sumo Logic reported a brief degradation in the Tracing Collection component in Australia, with latency in processing and displaying tracing data. The outage began at Sep 16, 2025 12:25 AM UTC and was resolved by Sep 16, 2025 1:20 AM UTC, lasting about 55 minutes. The incident affected the Tracing Collection / Australia component and was acknowledged with a transition from up to warn and back to up on the status page. The provider issued 2 status updates during the incident as they investigated and then resolved the issue, after which the service returned to normal.

Sumo Logic reported degraded performance affecting Open telemetry collectors in the North America 1 (US1) region. Users could experience latency when processing and displaying logs, metrics, and traces, with an increased likelihood of 5xx errors. The issue affected three US1 components: Tracing Collection, Logs Collection, and Metrics Collection. Sumo Logic issued two status updates during the incident, and the issue began at Sep 10, 2025 7:15 AM UTC and was resolved by Sep 10, 2025 9:15 AM UTC.

The Cloud Collection service in the North America 1 (US1) region experienced an outage that prevented users from adding, updating, or deleting Cloud Collection sources or collectors. The disruption was localized to Cloud Collection and affected ingestion and source-management workflows for customers relying on this service. The incident began at Aug 21, 2025 1:40 PM UTC when Sumo Logic indicated an investigation, and the service was restored by Aug 21, 2025 3:25 PM UTC. The outage lasted approximately 1 hour 45 minutes. The provider issued two status updates during the incident to communicate the investigation and recovery; impact appeared confined to the US1 region with no broader geographic spread.

Sumo Logic reported degraded performance for Cloud Collection in the North America 1 (US1) region, causing latency when retrieving data from cloud sources. The incident began at Aug 7, 2025 7:00 AM UTC and was resolved by Aug 7, 2025 7:45 AM UTC, with Cloud Collection moving from up to warn and back to up during the outage. The impact was limited to Cloud Collection in US1, affecting data ingestion workflows and dashboards relying on cloud-sourced data.

Sumo Logic experienced a temporary degradation affecting Logs Collection, Metrics Collection, and Tracing Collection in the Japan region. Users may have seen latency or errors when communicating with the API. The outage began at 6:25 AM UTC and was resolved by 7:05 AM UTC, lasting about 40 minutes. The incident prompted two status updates during the event as engineers investigated and worked to restore functionality.

Impact was localized to Japan, with all three components in that region affected.

A brief degraded performance incident affected Sumo Logic's Metrics Collection and Data Indexing in the North America 1 (US1) region. Users may have experienced latency in processing and displaying metrics data as the affected components reported issues. The outage began at 10:40 AM UTC and was resolved by 11:15 AM UTC, lasting roughly 35 minutes. The affected components were Metrics Collection / North America 1 (US1) and Data Indexing / North America 1 (US1).

The service provider issued 2 status updates during the incident, noting ongoing investigations and actions to restore normal operation. Impact was regional to North America 1 (US1).

Sumo Logic’s CSE UI in the North America 2 region (US2) briefly became unavailable due to a problem with the CSE UI, causing UI slowness for users. The outage began at Aug 4, 2025 9:35 PM UTC and was resolved by Aug 4, 2025 9:50 PM UTC, lasting about 15 minutes. The provider issued 2 status updates during the incident, describing the issue and then confirming recovery. The impact was limited to the CSE UI component in US2.

Sumo Logic experienced degraded performance in its o365 Collection, with latency in processing and displaying log data affecting Cloud Collection components in the AU and EU regions. The issue began at 6:15 AM UTC in AU and expanded to Europe 1 by 6:35 AM UTC, impacting log delivery and dashboards for users in those regions. The provider issued three status updates during the incident, and services were restored by 7:30 AM UTC.

The Sumo Logic CSE Processing Pipeline in Korea experienced latency in processing and displaying security data, resulting in degraded performance for users in the region. The incident began at Jul 29, 2025 4:10 PM UTC and was resolved about 30 minutes later at Jul 29, 2025 4:40 PM UTC, with the Korea component returning to normal after the brief issue. The provider listed the problem as "Problem with CSE Processing Pipeline" and communicated updates as the investigation progressed, noting latency in security data processing and display. The event affected a regional component (KR) and was resolved within the same region.