APM Charts Loading Slowly
Timeline · 1 update
- resolved Oct 20, 2026, 10:00 PM UTC
APM Charts for a subset of customers may have loaded slowly. Datapoint ingest was not affected.
SignalFx US0 had 59 outages in the last 2 years totaling 74h 54m of downtime — averaging 2.4 incidents per month.
There were 59 SignalFx US0 outages since September 29, 2025 totaling 74h 54m of downtime. Each is summarised below — incident details, duration, and resolution information.
APM Charts for a subset of customers may have loaded slowly. Datapoint ingest was not affected.
We are investigating a degradation of the Splunk Observability Cloud web application for some customers. Data ingest is not impacted at this time. We will provide an update as soon as possible.
Our engineering teams are actively troubleshooting the identified performance problems in the Splunk Observability Web UI, we will share a new update as soon as possible.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
We are monitoring recovery.
This incident has been resolved.
We are investigating a major outage of the Splunk Observability Cloud web application. Data ingest is not impacted at this time. We will provide an update as soon as possible.
The issue has been identified and a remediation is in progress.
Steps to remediation have recovered login access.
Customers may be experiencing delays in seeing newly created dimension, updated dimension, and alerts. Team is currently investigating the issue.
The issue has been identified and a fix is being implemented.
The issue has been identified and a remediation is in progress.
W have verified that the fix has recovered service.
We're experiencing connectivity issues with the Splunk Observability MCP server, which may affect the availability of some tools. We're actively investigating the issue
Our engineering teams continue troubleshooting connectivity issues with the Splunk Observability MCP server. We will share additional information as it becomes available.
Our engineering teams continue troubleshooting connectivity issues with the Splunk Observability MCP server. We will share additional information as it becomes available
Our engineering teams continue troubleshooting connectivity issues with the Splunk Observability MCP server. We will share additional information as it becomes available
Engineering teams have deployed a fix and service recovery is progressing. We will continue monitoring and share an update by 22:00 UTC.
We are continuing to monitor for any further issues.
Service recovery fully confirmed, we are now considering this resolved.
We are investigating delays in processing Splunk Observability Synthetic Monitoring test results. Synthetic Monitoring tests are operational but metrics may be missing until the issue is resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
This incident has been resolved.
We are seeing login failures due to certificate issues. It has been resolved.
Datapoint ingest is affected and we are dropping datapoints for new time-series. We are investigating and will provide an update every 15 mins.
Between 7:37 PM and 8:17 PM PST, a small number of data points for new time series were not accepted. As a result, new time series may have experienced a delay of approximately 20–25 minutes before becoming available in charting and detectors. APM and RUM ingestion were not impacted.
From 3:08PM PDT, customers may experience delays in seeing newly created MetricTimeSeries. Datapoint ingest is not affected. We are investigating and will provide an update shortly.
We've identified that this incident was a false alarm due to rate limiting applied to a single tenant. We have reached out to the affected tenant. All other customers within US0 are not and have not been impacted by this incident.
This incident has been resolved.
A degradation in the performance of the Splunk APM metrics processing pipeline is causing Monitoring MetricSets to be dropped. Trace data ingest is not impacted, but service, endpoint and workflow dashboards, and other charts and detectors built from Monitoring MetricSets are impacted.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
The issue has been fixed.
Some customers may have experienced delays in alert notifications from 4 am ~ 6 am (PST), 2026. Datapoint ingest is not affected. The issue is recovered.
We are currently investigating the issue. Certain APIs may be failing and active alert pages is loading slowly. No data is being dropped or lost.
The issue has been identified and the fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Between 4:45p - 6:45p PDT a very small percentage of metric data points were being dropped. This issue has been resolved.
Starting at 11:30a PDT, datapoint ingest is affected and we are dropping a small percentage of datapoints. We are investigating and will provide an update as progress is made.
We continue to investigate the issue affecting a small percentage of datapoint ingest in US0. Our engineering teams are actively working on the issue and evaluating potential mitigations. We will provide another update as more information becomes available.
We continue to investigate the issue affecting a small percentage of datapoint ingest in US0. Our engineering teams are actively working on the issue. We will provide another update as more information becomes available.
We have observed improvement in datapoint ingest in US0, and the rate of dropped datapoints has returned to expected levels. We are continuing to monitor the service closely to ensure stability. We will provide another update once monitoring is complete or if any additional issues are observed.
This incident has been resolved.
Starting at 6:48a PDT, Synthetic test runs are not able to be viewed in the user interface. Tests are still running and detectors are still working. We are investigating the issue and will send updates as progress is made.
The APM Profiling user interface is also unavailable at this time due to the same underlying issue. We are continuing to investigate and will provide updates as progress is made.
The data visible in the APM Profiling user interface is experiencing delays. Splunk Synthetics Monitoring is operational. We are continuing to investigate and will provide updates as progress is made.
This incident has been resolved.
Between 1a PDT and 2:50a PDT, any GCP integration that had the "Sync all (dynamically) listed projects" setting enabled had some of the Cloud Monitoring data from GCP dropped. This issue has been resolved. Customers may see gaps in charts and detectors that use affected GCP Cloud Monitoring metrics. AWS CloudWatch and Azure Monitor metrics are not impacted.
We are investigating a partial outage of the Splunk RUM Session Detail feature. Session data ingest is not impacted at this time. We will provide an update as soon as possible.
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.
This incident has been resolved.
Customers may be experiencing delays in some detectors. Datapoint ingest is not affected. We are investigating and will provide an update shortly.
We have identified the source of the issue and have taken mitigation actions. Recovery is in progress, and we are seeing gradual improvement. Our teams are continuing to investigate the underlying cause while monitoring the recovery. We will provide another update as more information becomes available.
The issue causing delays in some detectors has been resolved. Systems have recovered, and detector processing has returned to expected levels. Thank you for your patience while we worked to resolve this issue.
A degradation in the performance of the Splunk APM metrics processing pipeline is causing Monitoring MetricSets to be delayed by more than five minutes. Trace data ingest is not impacted, but service, endpoint and workflow dashboards, and other charts and detectors built from Monitoring MetricSets are impacted.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating a partial outage of the Splunk APM Tag Spotlight. Trace data ingest is not impacted at this time. We will provide an update as soon as possible.
Due to a regression in a recent release, users navigating from Logs Related Content on the APM TraceView page to Log Observer were redirected back to APM TraceView instead. This impacted the Logs Correlation experience for customers across all realms, except US3 and Gov. The change has been reverted to restore the expected navigation experience. Product availability for APM and Log Observer was not impacted; the issue was limited to the Logs Correlation workflow from TraceView. Incident Start Time: 05:09 PDT, June 25, 2026 Incident End Time: 22:15 PDT, June 25, 2026
We are investigating why Trace Lookups are failing for traces created between approximately 5:30am PT - 7:30am PT. Monitoring MetricSets and Troubleshooting MetricSets are not impacted. Metrics are still available. We are investigating the issue.
We are still investigating the issue.
We are continuing to investigate this issue.
The issue affecting Trace Lookup searchability for traces generated between approximately 5:30 AM and 7:30 AM PT on June 17 has been identified. This occurred during an approved maintenance window associated with repartitioning and scaling activities. Customers may be unable to search for traces generated during this timeframe. Trace ingestion and processing are operating normally, and traces generated outside of the affected window remain searchable. Our team has developed a fix and is currently validating it through internal testing. We expect validation to complete within approximately two hours and will provide another update once the fix is ready for deployment or as additional information becomes available.
We continue to make progress toward resolution. The fix is currently moving through the implementation process and will be rolled out once all deployment steps have been completed. We will provide another update as progress continues.
The fix has been successfully deployed, and we have confirmed that the issue affecting Trace Lookup searchability for traces generated between approximately 5:30 AM and 7:30 AM PT on June 17 has been resolved. Customers should now be able to search affected traces as expected.