Is SignalFx US1 down?

Beginning at 5:50 AM PDT, datapoint ingestion for the archival tier was impacted, resulting in a small number of datapoints not being accepted. The impact was limited to the archival tier. Detectors and charts were not affected. We have implemented remediation and are actively monitoring the system to ensure continued stability. We will provide updates every 15 minutes.

As of 7:48 AM PDT, we are no longer observing any data being dropped. The system is continuing to recover, and we are actively monitoring it to ensure continued stability.

The system is continuing to recover, and we are actively monitoring it to ensure continued stability.

The system is showing steady progress in its recovery. Our teams remain actively engaged, closely observing system metrics to ensure continued stability

We have successfully restored datapoint ingestion and are seeing steady progress as the data backlog is processed. We are actively monitoring this process to ensure full service functionality returns as quickly as possible.

We continue monitoring to ensure full service functionality.

We are continuing to monitor the system to ensure ongoing stability. Our teams remain actively engaged in observing performance metrics to confirm that all operations are functioning as expected.

To accelerate the recovery process, we are currently adding additional capacity to our clusters. Our teams remain actively engaged and are continuing to monitor system performance as it stabilizes.

The system has recovered and we ingesting archived data with no delay.

Datapoint ingest is affected and we are dropping datapoints some datapoints from 8:52 PDT. We are investigating and will provide an update every 15 mins.

Between 8:52 PDT and 9:47 PDT, a small number of data points for new time series were not accepted. As a result, new time series may have experienced a delay before becoming available in charting and detectors. Remediation is in place, and we are continuing to monitor the system to ensure stability.

The issue has been resolved, and datapoint ingestion is operating normally. We have confirmed that the system remains stable following remediation. This incident is now resolved.

A degradation of the trace data ingest path for Splunk APM is causing some trace spans to be dropped and lost. We are investigating the issue and will provide an update as soon as possible.

We are investigating a major outage of the Splunk Observability AI Assistant.

The issue has been identified as an Azure OpenAI outage and we are proceeding with a workaround.

A fix has been implemented and we are monitoring the results.

Monitoring phase complete. The issue has been resolved.

From 08/25/2026, 11:38AM PDT, a degradation in the performance of the Splunk APM trace processing pipeline is causing Troubleshooting 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; service-level and endpoint-level Monitoring MetricSets and the detectors built from them are also not impacted.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

Our teams continue monitoring the situation to ensure full remediation.

This incident has been resolved.