Splunk Observability Cloud US2 incident

Splunk APM Trace Data Ingestion Delayed

Minor Resolved View vendor source →

Splunk Observability Cloud US2 experienced a minor incident on August 5, 2026 affecting Splunk APM Trace Data, lasting 1h 42m. The incident has been resolved; the full update timeline is below.

Started
Aug 05, 2026, 01:53 AM UTC
Resolved
Aug 05, 2026, 03:35 AM UTC
Duration
1h 42m
Detected by Pingoru
Aug 05, 2026, 01:53 AM UTC

Affected components

Splunk APM Trace Data

Update timeline

  1. investigating Aug 05, 2026, 01:53 AM UTC

    A degradation in the performance of the Splunk APM data ingestion pipeline is causing the processing and storage of raw trace data to be delayed by more than five minutes. No data is being lost at this time and MetricSets are not impacted but the most recent data may not be available in trace search results.

  2. investigating Aug 05, 2026, 02:50 AM UTC

    We are continuing to investigate the degradation in the Splunk APM data ingestion pipeline. Processing and storage of raw trace data remains delayed by more than five minutes, so the most recent data may not be available in trace search results. No data is being lost at this time, and MetricSets are not impacted. Teams are working to restore normal processing and reduce ingestion delays.

  3. resolved Aug 05, 2026, 03:35 AM UTC

    The degradation in the Splunk APM data ingestion pipeline has been mitigated and is now resolved. Processing and storage of raw trace data has recovered, and recent data is available in trace search results. No data was lost, and MetricSets were not impacted. Thank you for your patience.