Sumo Logic

Affected: Billing and Account Management, Billing and Account Management, Billing and Account Management, Billing and Account Management

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-16 12:44 UTC

   We are currently investigating reports of problems with Billing and Account Management. We will provide more information soon.

2. identified 2026-10-16 14:04 UTC

   We have identified the source of the issue affecting Billing and Account Management. We are working on a fix for the problem.

3. resolved 2026-10-16 14:37 UTC

   We are no longer seeing issues with Billing and Account Management and normal operation has been restored at this time.

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Metrics Alerting

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-09 23:00 UTC

   We are currently investigating reports of problems with Metrics Alerting. Users may see processing of metrics data is delayed and metrics-based Monitors may have delayed triggers and notifications. All data is safely collected and will be processed as it was received. We will...

2. monitoring 2026-10-09 23:04 UTC

   We have implemented a fix for the issue affecting Metrics Alerting. Users relying on metrics-based alerts may have experience delayed delivery of notifications. Normal processing has resumed. We are currently monitoring the results.

3. resolved 2026-10-09 23:10 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-05 09:35 UTC

   We are currently investigating reports of problems with Cloud SIEM Processing. Log security records may take longer than normal to become searchable after processing. Users may not receive data when running queries or viewing dashboards that depend on recently collected data and...

2. identified 2026-10-05 10:25 UTC

   We have identified the source of the issue affecting Cloud SIEM Processing. Log security records may take longer than normal to become searchable after processing. Users may not receive data when running queries or viewing dashboards that depend on recently collected data and...

3. monitoring 2026-10-05 10:38 UTC

   We have implemented a fix for the issue affecting Cloud SIEM Processing. Log security records may take longer than normal to become searchable after processing. Users may not receive data when running queries or viewing dashboards that depend on recently collected data and...

4. resolved 2026-10-05 11:14 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-02 06:23 UTC

   We are currently investigating reports of problems with Cloud SIEM Processing. Logs may take longer than normal to become searchable after processing. Users may not receive data when running queries or viewing dashboards that depend on recently collected data and alerts may not...

2. identified 2026-10-02 07:11 UTC

   We have identified the source of the issue affecting Cloud SIEM Processing. Logs may take longer than normal to become searchable after processing. Users may not receive data when running queries or viewing dashboards that depend on recently collected data and alerts may not...

3. resolved 2026-10-02 07:28 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-01 13:36 UTC

   We are currently investigating reports of problems with Cloud SIEM Processing. Log security records may take longer than normal to become searchable after processing. Users may not receive data when running queries or viewing dashboards that depend on recently collected data and...

2. identified 2026-10-01 13:55 UTC

   We have identified the source of the issue affecting Cloud SIEM Processing. Logs may take longer than normal to become searchable after processing. Users may not receive data when running queries or viewing dashboards that depend on recently collected data and alerts may not...

3. resolved 2026-10-01 14:04 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-10-01 09:03 UTC

   We have implemented a fix for the issue affecting Cloud SIEM Processing. Log security records may take longer than normal to become searchable after processing. Users may not receive data when running queries or viewing dashboards that depend on recently collected data and...

2. resolved 2026-10-01 09:42 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Tracing Collection

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-27 01:22 UTC

   We are currently investigating reports of problems with Tracing Collection. Trace data sent may fail to ingest or be rejected due to service unavailability. We will provide more information soon.

2. monitoring 2026-09-27 01:34 UTC

   We have implemented a fix for the issue affecting Tracing Collection. We are currently monitoring the results.

3. resolved 2026-09-27 03:34 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-22 17:44 UTC

   We are currently investigating reports of problems with Cloud SIEM Processing. Log security records may take longer than normal to become searchable after processing. Users may not receive data when running queries or viewing dashboards that depend on recently collected data and...

2. monitoring 2026-09-22 17:56 UTC

   We have implemented a fix for the issue affecting Cloud SIEM Processing. We are currently monitoring the results.

3. resolved 2026-09-22 19:12 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM APIs, Cloud SIEM APIs, Cloud SIEM UI, Cloud SIEM UI

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-09-18 21:57 UTC

   We have identified the source of the issue affecting Cloud SIEM APIs and Cloud SIEM UI. The Cloud SIEM User Interface may fail to load or show errors. This can impact viewing Insights, managing detection rules, or investigating related signals and records. We are working on a...

2. monitoring 2026-09-18 21:59 UTC

   We have implemented a fix for the issue affecting Cloud SIEM APIs and Cloud SIEM UI. The Cloud SIEM User Interface may fail to load or show errors. This can impact viewing Insights, managing detection rules, or investigating related signals and records. We are currently...

3. resolved 2026-09-18 22:07 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-14 01:20 UTC

   We are currently investigating reports of problems with Cloud SIEM Processing. Users may experience delayed Signal Generation. Alerts based on signals may not dispatch to the user. We will provide more information soon.

2. monitoring 2026-09-14 01:40 UTC

   We have implemented a fix for the issue affecting Cloud SIEM Processing. Users may experience delayed Signal Generation. Alerts based on signals may not dispatch to the user. We are currently monitoring the results.

3. resolved 2026-09-14 01:50 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-11 10:24 UTC

   We are currently investigating reports of problems with Cloud SIEM Processing. Log security records may take longer than normal to become searchable after processing. Users may not receive data when running queries or viewing dashboards that depend on recently collected data and...

2. identified 2026-09-11 11:26 UTC

   We have identified the source of the issue affecting Cloud SIEM Processing. Log security records may take longer than normal to become searchable after processing. Users may not receive data when running queries or viewing dashboards that depend on recently collected data and...

3. monitoring 2026-09-11 11:33 UTC

   We have implemented a fix for the issue affecting Cloud SIEM Processing. Log security records may take longer than normal to become searchable after processing. Users may not receive data when running queries or viewing dashboards that depend on recently collected data and...

4. resolved 2026-09-11 11:52 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-07 20:41 UTC

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

2. identified 2026-09-07 20:42 UTC

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

3. monitoring 2026-09-07 20:51 UTC

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

4. resolved 2026-09-07 20:56 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM UI

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-04 07:38 UTC

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

2. resolved 2026-09-04 09:22 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-03 22:19 UTC

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

2. monitoring 2026-09-04 01:20 UTC

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

3. resolved 2026-09-04 02:36 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM Processing, Cloud SIEM Processing, Cloud SIEM Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-02 20:09 UTC

   We are currently investigating reports of problems with Cloud SIEM Processing. Users may experience delayed Signal Generation. Alerts based on signals may not dispatch to the user.

2. investigating 2026-09-02 20:14 UTC

   We are continuing to investigate this issue.

3. investigating 2026-09-02 20:36 UTC

   We are continuing to investigate this issue.

4. identified 2026-09-02 21:36 UTC

   We have identified the source of the issue affecting Cloud SIEM Processing. Users may experience delayed Signals and Insights Generation. Alerts based on signals may not dispatch to the user.

5. monitoring 2026-09-02 23:41 UTC

   We have implemented a fix for the issue affecting Cloud SIEM Processing. We are currently monitoring the results. Users may experience delayed Signals and Insights Generation. Alerts based on signals may not dispatch to the user.

6. monitoring 2026-09-02 23:47 UTC

   We are no longer seeing an issue with Cloud SIEM Processing in North America 2 (US2) and Europe 1 (EU). We are still actively monitoring the results on North America 1 (US1). Users may experience delayed Signals and Insights Generation. Alerts based on signals may not dispatch...

7. resolved 2026-09-03 03:15 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-19 17:44 UTC

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

2. identified 2026-08-19 18:15 UTC

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

3. monitoring 2026-08-19 18:23 UTC

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

4. resolved 2026-08-19 18:31 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Logs Collection, Metrics Collection, Tracing Collection

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-13 21:10 UTC

   We are currently investigating reports of problems with Logs Collection, Metrics Collection and Tracing Collection. The symptoms are: latency in processing and displaying log data, latency in processing and displaying metrics data, latency in processing and displaying tracing...

2. identified 2026-08-13 21:12 UTC

   We have identified the source of the issue affecting Logs Collection, Metrics Collection and Tracing Collection. The symptoms are: latency in processing and displaying log data, latency in processing and displaying metrics data, latency in processing and displaying tracing data....

3. monitoring 2026-08-13 21:32 UTC

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

4. resolved 2026-08-13 22:02 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Logs Alerting, Metrics Alerting

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-10 09:55 UTC

   We are currently investigating reports of problems with Logs Alerting and Metrics Alerting, which are resulting in latency, slowness, or delay in displaying data. We will provide more information soon.

2. identified 2026-08-10 09:57 UTC

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

3. resolved 2026-08-10 11:04 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM Processing, Data Indexing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-05 08:16 UTC

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

2. monitoring 2026-08-05 08:28 UTC

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

3. monitoring 2026-08-05 08:35 UTC

   We are continuing to monitor the fix for Data Indexing.

4. monitoring 2026-08-05 09:00 UTC

   We are continuing to monitor the fix for Data Indexing.

5. monitoring 2026-08-05 09:13 UTC

   We are also seeing impact on: Components: Cloud SIEM Processing We are continuing to monitor the fix for Cloud SIEM Processing and Data Indexing.

6. resolved 2026-08-05 09:22 UTC

   We are no longer seeing issues with Cloud SIEM Processing and Data Indexing and normal operation has been restored at this time.

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Logs Alerting

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-28 20:01 UTC

   We are currently investigating reports of problems with Logs Alerting. Users relying on logs based alerts may fail to receive notifications. We will provide more information soon.

2. identified 2026-07-28 20:15 UTC

   We have identified the source of the issue affecting logs based alerts. We are working on a fix for the problem.

3. resolved 2026-07-28 20:20 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Metrics Collection

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

Started during Azure: Network connectivity – Issues accessing resources in West US.

1. identified 2026-07-23 17:06 UTC

   We have identified the source of the issue affecting Microsoft Azure Metrics Collection. The symptoms are: latency in processing and displaying metrics data. This issue is caused by a networking problem on Microsoft Azure's infrastructure in the West US region, which is...

2. monitoring 2026-07-23 18:53 UTC

   Microsoft Azure has identified and rolled back a change that was causing the networking issue in the West US region. We are seeing signs of recovery in our Azure Metrics Collection pipeline and expect processing latency to return to normal shortly.

3. resolved 2026-07-23 19:11 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-22 09:21 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. monitoring 2026-07-22 10:05 UTC

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

3. resolved 2026-07-22 11:42 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Metrics Searches

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-14 03:19 UTC

   We are currently investigating reports of problems with Metrics Searches. Users relying on metrics queries may see errors when executing searches. The response team is investigating the issue and will update the status as we know more information.

2. monitoring 2026-07-14 05:32 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 2026-07-14 05:32 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-09 06:54 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. monitoring 2026-07-09 07:10 UTC

   We have implemented a fix for the issue affecting CSE Processing Pipeline. We are currently monitoring the results.

3. resolved 2026-07-09 07:21 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-18 19:37 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. monitoring 2026-06-18 19:53 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 2026-06-18 20:32 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Logs Searches

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-17 12:08 UTC

   We are currently investigating reports of problems with Log Searches. The symptoms are: error messages in log queries, specifically using the geoip operator.

2. identified 2026-06-17 12:13 UTC

   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.

3. resolved 2026-06-17 12:34 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Billing and Account Management

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-08 06:07 UTC

   We are currently investigating reports of problems with Billing and Account Management, which are resulting in latency, slowness, or delay in displaying data. We will provide more information soon.

2. monitoring 2026-06-08 06:24 UTC

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

3. resolved 2026-06-08 06:27 UTC

   We are no longer seeing issues with Billing and Account Management and normal operation has been restored at this time.

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM Processing

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-05 22:13 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 2026-06-05 22:14 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 2026-06-05 23:15 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Metrics Collection

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-02 14:04 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 2026-06-02 16:15 UTC

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

3. resolved 2026-06-02 17:44 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-22 12:56 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. resolved 2026-05-22 14:36 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Data Indexing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-22 08:33 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. [Identified] - 9:15 UTC We have identified the source of the issue affecting Data Indexing. The symptoms...

2. resolved 2026-05-22 10:26 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Metrics Collection

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-05-21 00:42 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.

2. resolved 2026-05-21 01:05 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Billing and Account Management, Billing and Account Management, Billing and Account Management, Billing and Account Management, Billing and Account Management, Billing and Account Management, Billing and Account Management, Billing and Account Management, Billing and Account Management, Billing and Account Management

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-05-08 10:50 UTC

   We have identified a technical issue affecting Billing and Account Management. Currently, Parent organisations are unable to manage Child organisations if a Mumbai (IN) region is included within the list. Our engineering team is actively developing a fix. We apologise for the...

2. identified 2026-05-08 11:37 UTC

   We are continuing to work on a fix for this issue.

3. resolved 2026-05-08 11:39 UTC

   We are no longer seeing issues with Billing and Account Management and normal operation has been restored at this time.

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM APIs, Cloud SIEM UI, Data Indexing, Metrics Alerting, Metrics Collection, Tracing Collection

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-05-08 01:27 UTC

   We have identified a failure of a cloud provider's availability zone as the source of the issue affecting CSE APIs, CSE UI, Data Indexing, Metrics Alerting, Metrics Collection and Tracing Collection. The symptoms are: latency in processing and displaying log data, latency in...

2. monitoring 2026-05-08 02:21 UTC

   Data Indexing, Tracing Ingestion, CSE UI, and CSE APIs have been restored. Metrics Ingestion and Metrics Alerting are recovering but not yet fully operational. Collection is not impacted — raw data continues to be ingested — however, there may be delays before it is available to...

3. resolved 2026-05-08 04:05 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-05 10:50 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 2026-05-05 11:23 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 2026-05-05 11:30 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM UI

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-04 12:26 UTC

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

2. resolved 2026-05-04 13:07 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Metrics Collection

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-22 14:32 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 2026-04-22 14:56 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 2026-04-22 15:10 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Logs Collection, Metrics Collection

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-14 16:40 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 2026-04-14 16:44 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 2026-04-14 16:50 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-04-09 09:54 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 2026-04-09 10:04 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 2026-04-09 10:10 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Metrics Searches

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-04-08 09:14 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 2026-04-08 09:42 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 2026-04-08 09:44 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Logs Collection

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-04-02 08:10 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 2026-04-02 08:20 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...

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Metrics Searches

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-23 17:03 UTC

   We are currently investigating reports of problems with Metrics Searches. The symptoms are: slowness in execution of metrics queries. We will provide more information soon.

2. identified 2026-03-23 17:53 UTC

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

3. monitoring 2026-03-23 18:03 UTC

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

4. resolved 2026-03-23 18:46 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-13 17:45 UTC

   We are currently investigating reports of problems with CSE Processing Pipeline. Log Security Records may take longer than normal to become searchable after processing. Users may not receive data when running queries or viewing dashboards that depend on recently collected data...

2. resolved 2026-03-13 18:52 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud Collection, Cloud Collection, Cloud Collection, Cloud Collection, Cloud Collection, Cloud Collection, Cloud Collection, Cloud Collection, Cloud Collection

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-26 12:45 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 2026-02-26 18:16 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 2026-02-26 18:23 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 2026-02-26 18:28 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Cloud SIEM Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-24 08:38 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 2026-02-24 09:24 UTC

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

3. monitoring 2026-02-24 09:55 UTC

   We have implemented a fix for the issue affecting CSE Processing Pipeline. We are currently monitoring the results.

4. resolved 2026-02-24 10:01 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Tracing Collection

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-17 17:19 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 2026-02-17 17:45 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 2026-02-17 17:54 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 2026-02-17 18:13 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Tracing Collection

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-15 09:41 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 2026-02-15 10:14 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 2026-02-15 10:19 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Metrics Collection

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-13 09:53 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 2026-02-13 10:37 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 2026-02-13 10:43 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Tracing Collection, Tracing Collection

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-13 08:53 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 2026-02-13 09:11 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 2026-02-13 09:32 UTC

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

Excerpts are shortened. Read the full incident on Sumo Logic's status page.

Affected: Data Indexing, Data Indexing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-23 10:18 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 2026-01-23 10:22 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 2026-01-23 10:42 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.

Excerpts are shortened. Read the full incident on Sumo Logic's status page.