- Level
- confirmed
- Worst impact
- Degraded
- Components
- Logs Searches
- Regions
- ca
What to do
Check whether you use Sumo Logic Logs Searches in ca. 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 26m it lasted.
Anything that failed between 2026-06-17 12:08 UTC and 2026-06-17 12:34 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 3
- investigating
We are currently investigating reports of problems with Log Searches. The symptoms are: error messages in log queries, specifically using the geoip operator.
provider
- identified
We have identified the source of the issue affecting Logs Searches. The symptoms are: error messages in log queries with the geoip operator. We are working on a fix for the problem.
provider
- resolved
We are no longer seeing issues with Logs Searches and normal operation has been restored at this time.
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-429b86d537
Is Sumo Logic still down?
No, this incident was resolved 2026-06-17 12:34 UTC. For Sumo Logic's live state, see https://down.guide/sumo-logic.
How long did it last?
26m, from 2026-06-17 12:08 UTC to 2026-06-17 12:34 UTC, by the times Sumo Logic posted.
What was affected?
Sumo Logic named Logs Searches in ca.
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.