- Level
- confirmed
- Worst impact
- Degraded
- Components
- Logs Collection
- Regions
- eu
What to do
Check whether you use Sumo Logic Logs Collection in eu. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 10m it lasted.
Anything that failed between 2026-04-02 08:10 UTC and 2026-04-02 08:20 UTC may need a replay.Subscribe to Sumo Logic's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=sumo-logic works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Sumo Logic 2
- monitoring
We have implemented a fix for the issue affecting Logs Collection. The symptoms are: latency in processing and displaying log data. We are currently monitoring the results.
provider
- resolved
We are no longer seeing issues with Logs Collection and normal operation has been restored at this time. [Update] Following further investigation, we determined that the previously communicated resolution time was incorrect. The correct resolution time has been updated to 8:20 AM UTC.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-985029bbf6
Is Sumo Logic still down?
No, this incident was resolved 2026-04-02 08:20 UTC. For Sumo Logic's live state, see https://down.guide/sumo-logic.
How long did it last?
10m, from 2026-04-02 08:10 UTC to 2026-04-02 08:20 UTC, by the times Sumo Logic posted.
What was affected?
Sumo Logic named Logs Collection in eu.
What caused it?
Sumo Logic hasn't published a root cause. If it does, it shows here.
Where does this come from?
Sumo Logic's official status page, https://status.sumologic.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.