Sumo Logic Outage History

Sumo Logic is up right now

There were 8 Sumo Logic outages since February 13, 2026 totaling 20h 22m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.sumologic.com

Minor April 22, 2026

Problem with Metrics Collection

Detected by Pingoru
Apr 22, 2026, 02:32 PM UTC
Resolved
Apr 22, 2026, 03:10 PM UTC
Duration
38m
Affected: Metrics Collection
Timeline · 3 updates
  1. investigating Apr 22, 2026, 05:41 PM UTC

    We are currently investigating reports of problems with Metrics Collection. The symptoms are: latency in processing and displaying metrics data. We will provide more information soon.

  2. monitoring Apr 22, 2026, 05:42 PM UTC

    We have implemented a fix for the issue affecting Metrics Collection. The symptoms are: latency in processing and displaying metrics data. We are currently monitoring the results.

  3. resolved Apr 22, 2026, 05:42 PM UTC

    We are no longer seeing issues with Metrics Collection and normal operation has been restored at this time.

Read the full incident report →

Minor April 14, 2026

Problem with Logs Collection and Metrics Collection

Detected by Pingoru
Apr 14, 2026, 04:40 PM UTC
Resolved
Apr 14, 2026, 04:50 PM UTC
Duration
9m
Affected: Logs CollectionMetrics Collection
Timeline · 3 updates
  1. investigating Apr 16, 2026, 08:03 AM UTC

    We are currently investigating reports of problems with Logs Collection and Metrics Collection. The symptoms are: latency in processing and displaying log data and latency in processing and displaying metrics data. We will provide more information soon.

  2. monitoring Apr 16, 2026, 08:03 AM UTC

    We have implemented a fix for the issue affecting Logs Collection and Metrics Collection. The symptoms are: latency in processing and displaying log data and latency in processing and displaying metrics data. We are currently monitoring the results.

  3. resolved Apr 16, 2026, 08:04 AM UTC

    We are no longer seeing issues with Logs Collection and Metrics Collection and normal operation has been restored at this time.

Read the full incident report →

Minor April 9, 2026

Problem with CSE Processing Pipeline

Detected by Pingoru
Apr 09, 2026, 09:54 AM UTC
Resolved
Apr 09, 2026, 10:10 AM UTC
Duration
16m
Affected: CSE Processing Pipeline
Timeline · 3 updates
  1. identified Apr 16, 2026, 08:01 AM UTC

    We have identified the source of the issue affecting CSE Processing Pipeline. The symptoms are: latency in processing and displaying security data. We are working on a fix for the problem.

  2. monitoring Apr 16, 2026, 08:01 AM UTC

    We have implemented a fix for the issue affecting CSE Processing Pipeline. The symptoms are: latency in processing and displaying security data. We are currently monitoring the results.

  3. resolved Apr 16, 2026, 08:01 AM UTC

    We are no longer seeing issues with CSE Processing Pipeline and normal operation has been restored at this time.

Read the full incident report →

Minor April 8, 2026

Problem with Metrics Searches

Detected by Pingoru
Apr 08, 2026, 09:14 AM UTC
Resolved
Apr 08, 2026, 09:44 AM UTC
Duration
30m
Affected: Metrics Searches
Timeline · 3 updates
  1. identified Apr 16, 2026, 07:57 AM UTC

    We have identified the source of the issue affecting Metrics Searches. The symptoms are: latency in processing and displaying metrics data. We are working on a fix for the problem.

  2. monitoring Apr 16, 2026, 07:57 AM UTC

    We have implemented a fix for the issue affecting Metrics Searches. The symptoms are: latency in processing and displaying metrics data. We are currently monitoring the results.

  3. resolved Apr 16, 2026, 07:57 AM UTC

    We are no longer seeing issues with Metrics Searches and normal operation has been restored at this time.

Read the full incident report →

Minor April 2, 2026

Problem with Logs Collection

Detected by Pingoru
Apr 02, 2026, 08:10 AM UTC
Resolved
Apr 02, 2026, 08:20 AM UTC
Duration
10m
Affected: Logs Collection
Timeline · 2 updates
  1. monitoring Apr 16, 2026, 07:54 AM UTC

    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.

  2. resolved Apr 16, 2026, 07:54 AM UTC

    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.

Read the full incident report →

Minor February 26, 2026

Problem with Cloud Collection

Detected by Pingoru
Feb 26, 2026, 12:45 PM UTC
Resolved
Feb 26, 2026, 06:28 PM UTC
Duration
5h 43m
Affected: Cloud CollectionCloud CollectionCloud CollectionCloud CollectionCloud CollectionCloud CollectionCloud CollectionCloud CollectionCloud CollectionCloud Collection
Timeline · 4 updates
  1. investigating Mar 27, 2026, 10:19 AM UTC

    We are currently investigating reports of problems with Cloud Collection for cloudSyslog Source. The symptoms are: latency in retrieving data from cloud. We will provide more information soon.

  2. identified Mar 27, 2026, 10:19 AM UTC

    We have identified the source of the issue affecting Cloud Collection, which are resulting in latency, slowness, or delay in displaying data. We are working on a fix for the problem.

  3. monitoring Mar 27, 2026, 10:19 AM UTC

    We have implemented a fix for the issue affecting Cloud Collection, which are resulting in latency, slowness, or delay in displaying data. We are currently monitoring the results.

  4. resolved Mar 27, 2026, 10:20 AM UTC

    We are no longer seeing issues with Cloud Collection and normal operation has been restored at this time.

Read the full incident report →

Minor February 17, 2026

Problem with Tracing Collection

Detected by Pingoru
Feb 17, 2026, 05:19 AM UTC
Resolved
Feb 17, 2026, 06:13 PM UTC
Duration
12h 53m
Affected: Tracing Collection
Timeline · 4 updates
  1. investigating Mar 27, 2026, 06:55 AM UTC

    We are currently investigating reports of problems with Tracing Collection. The symptoms are: latency in processing and displaying tracing data. We will provide more information soon.

  2. identified Mar 27, 2026, 06:55 AM UTC

    We have identified the source of the issue affecting Tracing Collection. The symptoms are: latency in processing and displaying tracing data. We are working on a fix for the problem.

  3. monitoring Mar 27, 2026, 06:55 AM UTC

    We have implemented a fix for the issue affecting Tracing Collection. The symptoms are: latency in processing and displaying tracing data. We are currently monitoring the results.

  4. resolved Mar 27, 2026, 06:56 AM UTC

    We are no longer seeing issues with Tracing Collection and normal operation has been restored at this time.

Read the full incident report →

Looking to track Sumo Logic downtime and outages?

Pingoru polls Sumo Logic's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Sumo Logic reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Sumo Logic alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Sumo Logic for free

5 free monitors · No credit card required