Sumo Logic outage history

Users relying on Sumo Logic Cloud SIEM Processing in North America 2 (US2) experienced degraded performance as log records took longer to become searchable after processing. Queries and dashboards depending on recently collected data could display incomplete results, and alerts may have been delayed. The issue began at 9:40 AM UTC and, by 10:26 AM UTC, the source was identified and a fix was being prepared. A remediation was implemented by 10:40 AM UTC with monitoring continuing, and services returned to normal by 11:15 AM UTC.

Users relying on Sumo Logic Cloud SIEM Processing in North America 2 (US2) faced degraded performance as logs took longer than normal to become searchable after processing. Queries and dashboards dependent on recently collected data could display incomplete results, and alerts may not dispatch. Impact began at 6:25 AM UTC and was localized to the US2 region.

At 7:20 AM UTC, Sumo Logic indicated that the issue source had been identified and a fix was being worked on for Cloud SIEM Processing. The service returned to a normal state by 7:30 AM UTC.

Sumo Logic reported a brief degradation in Cloud SIEM Processing in North America 2 (US2), causing logs to be slower to become searchable after processing. Users may not see data when running queries or viewing dashboards that rely on recently collected data, and alerts may not dispatch. Insights and signal generation could be delayed.

Impact began at 1:40 PM UTC; the issue was identified and a fix was being worked on by 2:00 PM UTC; service was restored by 2:05 PM UTC. This sequence indicates a roughly 25 minute window of degraded processing for the US2 Cloud SIEM components.

An issue in Sumo Logic's Cloud SIEM Processing in the North America 2 (US2) region caused degraded performance, with log security records taking longer to become searchable after processing. Users running queries or viewing dashboards that depend on recently collected data could see incomplete results and alerts for those records may be delayed. The incident began at 9:05 AM UTC and a fix was applied with monitoring ongoing, stabilizing as service returned to normal.

The US2 Cloud SIEM Processing component briefly moved from up to warn before returning to up, and the incident was resolved by 9:45 AM UTC after about forty minutes.

Users in the North America 2 (US2) region experienced issues with Sumo Logic Tracing Collection, with trace data potentially failing to ingest or being rejected due to service unavailability. The incident began at 1:25 AM UTC and affected the Tracing Collection component in US2 for a little over two hours.

Impact began at 5:45 PM UTC for Sumo Logic's Cloud SIEM Processing in North America 1 (US1). Some security logs took longer to become searchable after processing, and queries or dashboards relying on recently collected data could show stale information. Alerts may not dispatch promptly, and insights or signal generation on affected records were delayed. By 6:00 PM UTC, a fix was implemented and monitoring began, with services returning toward normal by 7:20 PM UTC.

In Europe 1 (EU) and Canada (CA), users experienced issues loading the Sumo Logic Cloud SIEM UI and API endpoints. This degraded the ability to view Insights, manage detection rules, and investigate signals and records. The disruption began at 10:00 PM UTC and affected the Cloud SIEM APIs and UI in the EU and CA regions. The impact was regional and brief.

Sumo Logic reported a brief degradation of Cloud SIEM Processing in North America 1 (US1), with users potentially experiencing delayed signal generation and alerts not reliably dispatching. The issue began at 1:25 AM UTC and a fix was implemented by 1:45 AM UTC, with monitoring indicating recovery by 1:55 AM UTC. The impact was localized to US1 and resolved in roughly half an hour, with services returning to normal after the incident.

Impact began at Sep 11, 2026 10:25 AM UTC in Australia as Sumo Logic reported problems with Cloud SIEM Processing. Log security records may take longer to become searchable after processing, and users running queries or viewing dashboards that rely on recently collected data might see delayed results. Alerts may not dispatch, and insights and signal generation could lag.

A fix was implemented at Sep 11, 2026 11:35 AM UTC and AU Cloud SIEM Processing returned to normal by Sep 11, 2026 11:55 AM UTC after monitoring results.

In Europe 1 (EU), Sumo Logic's Cloud SIEM Processing experienced latency in processing and displaying security data, causing delayed visibility in dashboards and alerts. The issue began at 8:45 PM UTC and was identified as a regional problem affecting Cloud SIEM Processing in Europe 1. A fix was implemented by 8:55 PM UTC, and monitoring confirmed the service returned to normal by 9:00 PM UTC.