Skip to content
Sumo Logic logo

Other

Is Sumo Logic down right now?

NormalOfficial status last polled Oct 4, 2026 17:24 UTCwww.sumologic.comOfficial status page

Are you on the Sumo Logic team and see something inaccurate? Report it to us. We respond within one business day.

Is Sumo Logic down right now?

No. Sumo Logic has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 4, 2026 17:27 UTC

Normal

Sumo Logic is operating normally

As of Oct 4, 2026 17:27 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

0

Last incident

Oct 2, 2026 08:31 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unavailable

Current measurements are not available for a health score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Sumo Logic.

4

Incident days

26

No recorded incident

4h 4m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Sumo Logic. Hover a day for detail.

Sep 5Sep 10Sep 15Sep 20Sep 25Sep 3001234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

4

Days with incidents

1 incident

Busiest day

4h 4m

Recorded duration

Report volume

0 reports in last 24H

05:15 PM08:45 PM12:15 AM03:45 AM07:15 AM10:45 AM02:15 PM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Sumo Logic: vendor-reported minor incident on October 2 (tracked 1h 24m)

Oct 2, 07:06 AM → Oct 2, 08:31 AM · 1h 24m · medium

Sumo Logic reported a minor-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 1h 24m, from Fri, 02 Oct 2026 07:06:56 GMT to Fri, 02 Oct 2026 08:31:10 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
1h 24m
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The vendor's own status page is the only source PulseWatch has for it.

Incident timeline

  1. Oct 2, 07:06 AM

    The vendor reported a minor-impact incident on its own status page; PulseWatch began tracking it

  2. Oct 2, 07:06 AM

    Status updated: possible issue

  3. Oct 2, 08:31 AM

    PulseWatch closed the incident

Official updates

  1. Oct 2, 07:06 AM

    Sumo Logic reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.

Reliability

Detected by PulseWatch

30-day uptime

99.43%

90-day uptime

99.16%

Calculated from Sumo Logic's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other other services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedMedium

Sumo Logic: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

10/2/2026, 7:06:56 AM · 1h 24m

07:06 AM08:31 AM
Detection10/2/2026, 7:06:56 AM · 2d ago

Detected — medium severity

Sumo Logic: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

Sumo Logic: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/27/2026, 2:35:48 AM · 1h 30m

02:35 AM04:05 AM
Detection9/27/2026, 2:35:48 AM · 7d ago

Detected — medium severity

Sumo Logic: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

Sumo Logic: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/22/2026, 7:01:35 PM · 15 min

07:01 PM07:16 PM
Detection9/22/2026, 7:01:35 PM · 11d ago

Detected — medium severity

Sumo Logic: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedHigh

Sumo Logic: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Sumo Logic or have an alert rule on it can be alerted, labelled vendor-reported.

9/18/2026, 10:02:09 PM · 54 min

10:02 PM10:56 PM
Detection9/18/2026, 10:02:09 PM · 15d ago

Detected — high severity

Sumo Logic: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Sumo Logic or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedMedium

Sumo Logic incident correlated across 1 signal group: official/vendor.

9/4/2026, 8:07:13 AM · 1h 44m

08:07 AM09:52 AM
Detection9/4/2026, 8:07:13 AM · 1mo ago

Detected — medium severity

Sumo Logic incident correlated across 1 signal group: official/vendor.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Sumo Logic enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Normal
Monitoring
Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).
Coverage
Verified against the vendor's own incident history
Reports (24h)
0
Baseline / hour
5
Open threshold
3x

Official site

www.sumologic.com