SignalFx US0 incident

Splunk APM Troubleshooting MetricSets and Monitoring MetricSets Delayed

Major Resolved View vendor source →

SignalFx US0 experienced a major incident on June 15, 2026 affecting Splunk APM Troubleshooting MetricSets and Splunk APM Trace Data and 1 more component, lasting 6h 18m. The incident has been resolved; the full update timeline is below.

Started
Jun 15, 2026, 05:53 PM UTC
Resolved
Jun 16, 2026, 12:12 AM UTC
Duration
6h 18m
Detected by Pingoru
Jun 15, 2026, 05:53 PM UTC

Affected components

Splunk APM Troubleshooting MetricSetsSplunk APM Trace DataSplunk APM Tag SpotlightSplunk APM Business Workflows

Update timeline

  1. investigating Jun 15, 2026, 05:53 PM UTC

    A degradation in the performance of the Splunk APM trace processing pipeline is causing Troubleshooting MetricSets and Monitoring MetricSets to be delayed by more than five minutes. As a result, the APM Troubleshooting experience, service maps and Tag Spotlight do not have access to the most recent data. The processing of metrics for Business Workflows, which also depends on this pipeline, are equally delayed. Trace data ingest is not impacted at this time.

  2. investigating Jun 15, 2026, 06:37 PM UTC

    Efforts to address the pipeline performance degradation are ongoing.

  3. investigating Jun 15, 2026, 07:07 PM UTC

    We are continuing to work on the performance degradation affecting the Splunk APM trace processing pipeline. Our teams are actively working to restore normal service, and we will provide further updates as more information becomes available.

  4. investigating Jun 15, 2026, 07:40 PM UTC

    There is no change in status. Our teams continue to work on resolving the performance degradation in the Splunk APM trace processing pipeline. Delays of over five minutes in Troubleshooting and Monitoring MetricSets persist. We will provide further updates as soon as more information is available.

  5. identified Jun 15, 2026, 08:16 PM UTC

    We have identified the root cause of the performance degradation in the Splunk APM trace processing pipeline. Our engineering teams are currently planning the most efficient approach to implement a fix and restore normal service functionality. We will provide further updates as we move into the implementation phase.

  6. identified Jun 15, 2026, 08:48 PM UTC

    Our teams are continuing to finalize the implementation plan for the fix to address the performance degradation in the Splunk APM trace processing pipeline. We will provide further updates as we move into the implementation phase.

  7. identified Jun 15, 2026, 09:20 PM UTC

    There is no change in status to report. Our engineering teams are currently finalizing the remediation strategy to address the performance degradation within the Splunk APM trace processing pipeline. We are prioritizing a stable resolution.

  8. identified Jun 15, 2026, 09:53 PM UTC

    Our engineering teams are working diligently to ensure the proposed fix for the Splunk APM trace processing pipeline is executed effectively to restore normal service.

  9. identified Jun 15, 2026, 10:32 PM UTC

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

  10. identified Jun 15, 2026, 11:04 PM UTC

    Efforts to improve the pipeline performance, including monitoring metrics pipeline management capabilities such as aggregation, filtering, and archiving, are ongoing.

  11. identified Jun 15, 2026, 11:35 PM UTC

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

  12. resolved Jun 16, 2026, 12:12 AM UTC

    This incident has been resolved as latency has dropped to a normal threshold.