Is Sumo Logic Down?

No — Sumo Logic is up

Reachable from all 8 checked regions

Average response time: 104ms

Last checked 49 minutes ago · checks run every 6 hours

Official status page: https://status.sumologic.com

Sumo Logic uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

146ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 56 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

56-day clean streak

Sep 14 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

374ms

DNS 142ms TCP 2ms TLS 5ms TTFB 367ms

arn

59ms

DNS 38ms TCP 0ms TLS 5ms TTFB 54ms

cdg

67ms

DNS 37ms TCP 1ms TLS 7ms TTFB 61ms

dfw

91ms

DNS 46ms TCP 0ms TLS 5ms TTFB 86ms

ewr

53ms

DNS 29ms TCP 1ms TLS 6ms TTFB 49ms

fra

85ms

DNS 57ms TCP 1ms TLS 6ms TTFB 79ms

syd

26ms

DNS 8ms TCP 0ms TLS 5ms TTFB 23ms

yyz

80ms

DNS 39ms TCP 1ms TLS 4ms TTFB 75ms

What Sumo Logic does

Sumo Logic is a cloud log management and analytics platform, also sold as a SIEM for security operations. Applications and infrastructure ship logs and metrics into it, and teams query them, build dashboards and run alerts. Each customer is placed in a named deployment such as US1, US2, EU or AU, which determines where their data lives.

What an outage looks like

Search returns errors or takes far longer than usual, and dashboards fail to populate. Ingestion problems mean recent logs are missing from results while collectors keep sending, so a query for the last hour comes back thin. Scheduled searches and alerts fire late or not at all. Login through the web interface or the API may fail for one deployment only.

What to do about it

status.sumologic.com is organised by deployment: North America 1 (US1), North America 2 (US2), Europe 1 (EU), Europe 2 (DE), Australia (AU), Japan, Canada, Korea, Zurich, America Federal and the European Sovereign Cloud each carry their own APIs, Authentication and related components. Read only your deployment. Leave collectors running, since they buffer and catch up rather than discarding data.

Is it down for everyone, or just you?

If this page says Sumo Logic is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Sumo Logic outage FAQ

Which Sumo Logic deployment am I on?

It is visible in the URL you log into, and it decides which section of the status page applies to you. Sumo Logic runs separate deployments including US1, US2, EU, DE, AU, JP, CA, KR, CH, FED and the European Sovereign Cloud, each reported independently. An incident in one says nothing about the others, so reading the wrong section is the most common mistake here.

My last-hour query looks empty. Did logging stop?

Check ingestion for your deployment. Collectors can keep sending while the platform is behind on indexing, so recent data is absent from search results and then appears once processing catches up. Query a longer window to see whether the gap has an end, and avoid concluding an application went quiet based on a search run during an incident.

Will alerts that should have fired during an outage fire afterwards?

Not reliably. Scheduled searches and alerting are affected by both ingestion delays and search problems, so notifications can be late, duplicated, or missed entirely. Treat the incident window as unmonitored, and re-run the relevant searches by hand once your deployment recovers rather than assuming that no alert means nothing happened.

Should I stop my collectors during an incident?

No. Collectors buffer data locally when they cannot reach the service and send it when the connection returns, so leaving them running is what preserves the logs. Stopping them creates a real gap that cannot be filled in later. Keep an eye on local disk on busy hosts during a long incident, since buffered data accumulates there.

How we measure this

We request Sumo Logic's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Sumo Logic publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Sumo Logic goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required