Sumo Logic US1 Outage History

Sumo Logic US1 is up right now

Pingoru has recorded 52 incidents for Sumo Logic US1: 52 in the last 12 months and 20 in the last 90 days.

Source: status.sumologic.com

52incidents recorded
52last 12 months
20last 90 days
94 minutestypical duration
Incidents per month
0510AprMayJunJulAugSepOct6
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct1%
Pingoru began tracking Sumo Logic US1 in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202663 of 720 (0%)
May 202679 of 744 (1%)
June 202656 of 720 (1%)
July 202657 of 744 (1%)
August 202644 of 744 (1%)
September 2026919 of 720 (3%)
October 202666 of 586 (1%)

Incidents, newest first

Minor May 5, 2026 Problem with CSE Processing Pipeline in America Federal (FED) 40m Cloud SIEM Processing

Started May 05, 2026, 10:50 AM UTC· resolved May 05, 2026, 11:30 AM UTC

  1. investigating May 05, 2026, 10:50 AM UTC

    We are currently investigating reports of problems with CSE Processing Pipeline. The symptoms are: latency in processing and displaying security data. We will provide more information soon.

  2. identified May 05, 2026, 11:23 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.

  3. resolved May 05, 2026, 11:30 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 May 4, 2026 Problem with CSE UI in North America 2 (US2) 41m Cloud SIEM UI

Started May 04, 2026, 12:26 PM UTC· resolved May 04, 2026, 01:07 PM UTC

  1. investigating May 04, 2026, 12:26 PM UTC

    We are currently investigating reports of problems with CSE UI. The symptoms are: UI slowness. We will provide more information soon.

  2. resolved May 04, 2026, 01:07 PM UTC

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

Read the full incident report →

Minor April 19, 2026 Degraded Performance detected on status page 1h 39m Overall

Started Apr 19, 2026, 09:14 PM UTC· resolved Apr 19, 2026, 10:54 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor April 14, 2026 Problem with Logs Collection and Metrics Collection in North America 1 (US1) 9m Logs Collection, Metrics Collection

Started Apr 14, 2026, 04:40 PM UTC· resolved Apr 14, 2026, 04:50 PM UTC

  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 in Canada (CA) 16m Cloud SIEM Processing

Started Apr 09, 2026, 09:54 AM UTC· resolved Apr 09, 2026, 10:10 AM UTC

  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 in Europe 1 (EU) 30m Metrics Searches

Started Apr 08, 2026, 09:14 AM UTC· resolved Apr 08, 2026, 09:44 AM UTC

  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 in Europe 1 (EU) 10m Logs Collection

Started Apr 02, 2026, 08:10 AM UTC· resolved Apr 02, 2026, 08:20 AM UTC

  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 in India (IN), North America 1 (US1), North America 2 (US2), Europe 1 (EU), Europe 2 (DE), Australia (AU), Japan (JP), Canada (CA), Korea (KR), and America Federal (FED) 5h 43m Cloud Collection, Cloud Collection, Cloud Collection, Cloud Collection and 5 more

Started Feb 26, 2026, 12:45 PM UTC· resolved Feb 26, 2026, 06:28 PM UTC

  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 in North America 1 (US1) 12h 53m Tracing Collection

Started Feb 17, 2026, 05:19 AM UTC· resolved Feb 17, 2026, 06:13 PM UTC

  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 →

Minor February 15, 2026 Problem with Tracing Collection in Australia (AU) 38m Tracing Collection

Started Feb 15, 2026, 09:41 AM UTC· resolved Feb 15, 2026, 10:19 AM UTC

  1. investigating Mar 27, 2026, 06:52 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. monitoring Mar 27, 2026, 06:52 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.

  3. resolved Mar 27, 2026, 06:52 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 →

Critical February 13, 2026 Problem with Metrics Collection in Australia (AU) 50m Metrics Collection

Started Feb 13, 2026, 09:53 AM UTC· resolved Feb 13, 2026, 10:43 AM UTC

  1. investigating Mar 27, 2026, 10:13 AM 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 Mar 27, 2026, 10:13 AM 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 Mar 27, 2026, 10:13 AM 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 February 13, 2026 Problem with Tracing Collection in Europe 2 (DE) and Australia (AU) 38m Tracing Collection, Tracing Collection

Started Feb 13, 2026, 08:53 AM UTC· resolved Feb 13, 2026, 09:32 AM UTC

  1. investigating Mar 27, 2026, 06:45 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. monitoring Mar 27, 2026, 06:46 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.

  3. resolved Mar 27, 2026, 06:47 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 →

Minor January 23, 2026 Problem with Data Indexing in North America 2 (US2) and North America 1 (US1) 24m Data Indexing, Data Indexing

Started Jan 23, 2026, 10:18 AM UTC· resolved Jan 23, 2026, 10:42 AM UTC

  1. investigating Mar 27, 2026, 05:06 AM UTC

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

  2. identified Mar 27, 2026, 05:07 AM UTC

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

  3. resolved Mar 27, 2026, 05:07 AM UTC

    We are no longer seeing issues with Data Indexing and normal operation has been restored at this time. [Update] We have updated this incident to include North America 2 (US2) as an impacted deployment.

Read the full incident report →

Minor January 22, 2026 Problem with Metrics Alerting in North America 1 (US1) 41m Metrics Alerting

Started Jan 22, 2026, 05:50 AM UTC· resolved Jan 22, 2026, 06:32 AM UTC

  1. investigating Mar 27, 2026, 04:52 AM UTC

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

  2. identified Mar 27, 2026, 04:54 AM UTC

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

  3. monitoring Mar 27, 2026, 04:54 AM UTC

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

  4. resolved Mar 27, 2026, 04:54 AM UTC

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

Read the full incident report →