Live / Sumo Logic / Incident
Sumo Logic: Problem with Cloud SIEM Processing in North America 2 (US2)
Sumo Logic · sumologic.comMinor incidentResolved2026-10-05 11:14 UTC
Public — what happened
Summary
Sumo Logic said it saw problems with Cloud SIEM Processing in its North America 2 (US2) region beginning at 09:35 UTC on October 5, 2026, rating the incident as minor. According to the company, security log records could become searchable later than usual, and queries, dashboards and alerts relying on recent data might return nothing or fail to send, with insights and signals also delayed. Sumo Logic reported finding the source of the problem at 10:25 UTC without describing it, applied a fix at 10:38 UTC, and marked the incident resolved at 11:14.
Affected
Cloud SIEM Processing
Timeline
- Started — 2026-10-05 09:35 UTC
- Investigating — 2026-10-05 09:35 UTC
- Identified — 2026-10-05 10:25 UTC
- Monitoring — 2026-10-05 10:38 UTC
- Resolved — 2026-10-05 11:14 UTC · 1h 40m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Sumo Logic against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Sumo Logic: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Sumo Logic report →
More from Sumo Logic
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.