SignalFx US0 Outage History
SignalFx US0 is up right nowPingoru has recorded 106 incidents for SignalFx US0: 89 in the last 12 months and 13 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 6 | 195 of 720 (27%) |
| May 2026 | 2 | 1 of 744 (0%) |
| June 2026 | 10 | 48 of 720 (7%) |
| July 2026 | 13 | 47 of 744 (6%) |
| August 2026 | 1 | 1 of 744 (0%) |
| September 2026 | 3 | 3 of 720 (0%) |
| October 2026 | 8 | 21 of 528 (4%) |
Incidents, newest first
Minor October 20, 2026 APM UI Degraded 33m Splunk APM Interface
Started Oct 20, 2026, 07:28 PM UTC· resolved Oct 20, 2026, 08:01 PM UTC
- investigating Oct 20, 2026, 10:16 PM UTC
APM UI for a subset of customers may be have degraded experience. We are investigating and will provide an update shortly.
- identified Oct 20, 2026, 10:16 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Oct 20, 2026, 10:17 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 20, 2026, 10:18 PM UTC
This incident has been resolved.
Major October 20, 2026 APM Charts Loading Slowly 12h
Started Oct 20, 2026, 07:30 AM UTC· resolved Oct 20, 2026, 07:30 PM UTC
- resolved Oct 20, 2026, 10:00 PM UTC
APM Charts for a subset of customers may have loaded slowly. Datapoint ingest was not affected.
Minor October 15, 2026 Splunk Observability Cloud Web Interface Degradation 2h 24m Splunk Observability Cloud Web Interface
Started Oct 15, 2026, 06:55 PM UTC· resolved Oct 15, 2026, 09:20 PM UTC
- investigating Oct 15, 2026, 06:55 PM UTC
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.
- investigating Oct 15, 2026, 08:00 PM UTC
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.
- monitoring Oct 15, 2026, 08:33 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 15, 2026, 09:20 PM UTC
This incident has been resolved.
Minor October 12, 2026 Splunk APM Trace Data Ingestion Delayed 1h 53m Splunk APM Trace Data
Started Oct 12, 2026, 07:48 PM UTC· resolved Oct 12, 2026, 09:42 PM UTC
- identified Oct 12, 2026, 07:48 PM 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.
- monitoring Oct 12, 2026, 09:00 PM UTC
We are monitoring recovery.
- resolved Oct 12, 2026, 09:42 PM UTC
This incident has been resolved.
Critical October 7, 2026 Splunk Observability Cloud Web Interface Unavailable 41m Splunk Observability Cloud Web Interface
Started Oct 07, 2026, 08:39 PM UTC· resolved Oct 07, 2026, 09:20 PM UTC
- investigating Oct 07, 2026, 08:39 PM UTC
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.
- identified Oct 07, 2026, 09:12 PM UTC
The issue has been identified and a remediation is in progress.
- resolved Oct 07, 2026, 09:20 PM UTC
Steps to remediation have recovered login access.
Major October 7, 2026 Newly created dimension, updated dimension, and alerts may be delayed 1h 4m Splunk Observability Cloud Web Interface, Alerting
Started Oct 07, 2026, 08:18 PM UTC· resolved Oct 07, 2026, 09:23 PM UTC
- investigating Oct 07, 2026, 08:18 PM UTC
Customers may be experiencing delays in seeing newly created dimension, updated dimension, and alerts. Team is currently investigating the issue.
- identified Oct 07, 2026, 08:25 PM UTC
The issue has been identified and a fix is being implemented.
- identified Oct 07, 2026, 09:12 PM UTC
The issue has been identified and a remediation is in progress.
- resolved Oct 07, 2026, 09:23 PM UTC
W have verified that the fix has recovered service.
Minor October 7, 2026 Splunk Observability MCP Tools are not loading 2h 49m MCP
Started Oct 07, 2026, 06:46 PM UTC· resolved Oct 07, 2026, 09:35 PM UTC
- investigating Oct 07, 2026, 06:46 PM UTC
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
- investigating Oct 07, 2026, 07:16 PM UTC
Our engineering teams continue troubleshooting connectivity issues with the Splunk Observability MCP server. We will share additional information as it becomes available.
- investigating Oct 07, 2026, 07:59 PM UTC
Our engineering teams continue troubleshooting connectivity issues with the Splunk Observability MCP server. We will share additional information as it becomes available
- investigating Oct 07, 2026, 08:36 PM UTC
Our engineering teams continue troubleshooting connectivity issues with the Splunk Observability MCP server. We will share additional information as it becomes available
- monitoring Oct 07, 2026, 09:12 PM UTC
Engineering teams have deployed a fix and service recovery is progressing. We will continue monitoring and share an update by 22:00 UTC.
- monitoring Oct 07, 2026, 09:13 PM UTC
We are continuing to monitor for any further issues.
- resolved Oct 07, 2026, 09:35 PM UTC
Service recovery fully confirmed, we are now considering this resolved.
Minor October 3, 2026 Splunk Observability Synthetic Metric may be missing 51m Splunk Synthetics Monitoring Results processing
Started Oct 03, 2026, 02:20 AM UTC· resolved Oct 03, 2026, 03:12 AM UTC
- investigating Oct 03, 2026, 02:55 AM UTC
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.
- identified Oct 03, 2026, 03:03 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Oct 03, 2026, 03:12 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 03, 2026, 03:12 AM UTC
This incident has been resolved.
Minor September 25, 2026 APM Troubleshooting metrics are delayed up to 3h 2h 32m Splunk APM Interface
Started Sep 25, 2026, 12:34 PM UTC· resolved Sep 25, 2026, 03:07 PM UTC
- investigating Sep 25, 2026, 12:34 PM UTC
We are currently investigating this issue.
- identified Sep 25, 2026, 01:00 PM UTC
The issue has been identified and a fix is being implemented.
- identified Sep 25, 2026, 02:02 PM UTC
We are continuing to work on a fix for this issue.
- resolved Sep 25, 2026, 03:07 PM UTC
This incident has been resolved.
Minor September 18, 2026 Potential Login Issues –
Started Sep 18, 2026, 03:00 PM UTC· resolved Sep 18, 2026, 03:00 PM UTC
- resolved Sep 18, 2026, 03:07 PM UTC
We are seeing login failures due to certificate issues. It has been resolved.
Minor September 12, 2026 Datapoints Being Dropped 14m Datapoint Ingest
Started Sep 12, 2026, 03:16 AM UTC· resolved Sep 12, 2026, 03:30 AM UTC
- investigating Sep 12, 2026, 03:16 AM UTC
Datapoint ingest is affected and we are dropping datapoints for new time-series. We are investigating and will provide an update every 15 mins.
- resolved Sep 12, 2026, 03:30 AM UTC
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.
Major August 24, 2026 MetricTimeSeries Creation Delayed 1h 11m Alerting
Started Aug 24, 2026, 11:09 PM UTC· resolved Aug 25, 2026, 12:20 AM UTC
- investigating Aug 24, 2026, 11:09 PM UTC
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.
- investigating Aug 25, 2026, 12:20 AM UTC
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.
- resolved Aug 25, 2026, 12:20 AM UTC
This incident has been resolved.
Critical July 31, 2026 Splunk APM Monitoring MetricSets dropped 46m Splunk APM Interface, Splunk APM Monitoring MetricSets
Started Jul 31, 2026, 03:46 AM UTC· resolved Jul 31, 2026, 04:32 AM UTC
- investigating Jul 31, 2026, 03:46 AM UTC
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.
- identified Jul 31, 2026, 04:07 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jul 31, 2026, 04:08 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 31, 2026, 04:32 AM UTC
The issue has been fixed.
Notice July 24, 2026 Alert Notification Delayed –
Started Jul 24, 2026, 11:00 AM UTC· resolved Jul 24, 2026, 11:00 AM UTC
- resolved Jul 24, 2026, 03:59 PM UTC
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.
Major July 15, 2026 Splunk Observability APIs Errors and Active Alerts Page is Loading Slowly 3h 39m Splunk Observability Cloud API, Alerting
Started Jul 15, 2026, 12:20 PM UTC· resolved Jul 15, 2026, 04:00 PM UTC
- investigating Jul 15, 2026, 12:20 PM UTC
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.
- identified Jul 15, 2026, 12:48 PM UTC
The issue has been identified and the fix is being implemented.
- monitoring Jul 15, 2026, 02:57 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 15, 2026, 04:00 PM UTC
This incident has been resolved.
Minor July 10, 2026 New time series may be delayed in joining detectors in US0 1d 6h Alerting
Started Jul 10, 2026, 12:03 PM UTC· resolved Jul 11, 2026, 06:09 PM UTC
- investigating Jul 10, 2026, 12:03 PM UTC
Starting at 1a PDT, a small percentage of detectors may have missed firing. No data has been lost. We are investigating and will provide an update shortly.
- monitoring Jul 10, 2026, 12:05 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Jul 10, 2026, 12:47 PM UTC
We are continuing to monitor for any further issues.
- monitoring Jul 10, 2026, 01:51 PM UTC
We are continuing to monitor for any further issues.
- investigating Jul 10, 2026, 02:52 PM UTC
We have seen a return of a small percentage of detectors that may not be firing. No data is lost. We are continuing to investigate.
- investigating Jul 10, 2026, 03:52 PM UTC
We continue to investigate an issue affecting a small percentage of detectors in US0 that may not have fired as expected. No data loss has been observed. Our engineering teams are actively investigating the issue, and we will provide another update as more information becomes available.
- investigating Jul 10, 2026, 04:53 PM UTC
We continue to investigate an issue affecting a small percentage of detectors in US0 that may not have fired as expected. No data loss has been observed. Our engineering teams are actively investigating the issue, and we will provide another update as more information becomes available.
- investigating Jul 10, 2026, 06:01 PM UTC
We continue to investigate an issue affecting a small percentage of detectors in US0 that may not have fired as expected. No data loss has been observed. Our engineering teams are actively investigating the issue, and we will provide another update as more information becomes available.
- investigating Jul 10, 2026, 07:02 PM UTC
We continue to investigate an issue affecting a small percentage of detectors in US0 that may not have fired as expected. No data loss has been observed. Our engineering teams are actively investigating the issue, and we will provide another update as more information becomes available.
- identified Jul 10, 2026, 07:39 PM UTC
A mitigation has been applied for the issue affecting a small percentage of detectors in US0 that may not have fired as expected. We are observing continued recovery and are monitoring the environment to ensure the mitigation is fully effective. No data loss has been observed. We will provide another update once recovery is complete.
- identified Jul 10, 2026, 08:53 PM UTC
We are observing continued recovery and are monitoring the environment to ensure the mitigation is fully effective. No data loss has been observed. We will provide another update once recovery is complete.
- monitoring Jul 10, 2026, 10:09 PM UTC
We are observing continued recovery and are monitoring the environment to ensure the mitigation is fully effective. No data loss has been observed. We will provide another update once recovery is complete.
- monitoring Jul 10, 2026, 11:06 PM UTC
We are observing continued recovery and are monitoring the environment to ensure the mitigation is fully effective. No data loss has been observed. We will provide another update once recovery is complete.
- monitoring Jul 11, 2026, 12:16 AM UTC
We are observing continued recovery and are monitoring the environment to ensure the mitigation is fully effective. No data loss has been observed. We will provide another update once recovery is complete.
- identified Jul 11, 2026, 02:15 AM UTC
We have applied mitigations that reduced the impact, but recovery is not yet complete. A small percentage of detectors in US0 may still not be firing as expected due to delayed processing. No data loss has been observed. Engineering teams continue to investigate towards the additional mitigations. We will provide another update as more information becomes available.
- identified Jul 11, 2026, 03:03 AM UTC
We have identified that newly created time series in US0 may take up to 10 minutes to be included in detectors, which may delay detector evaluations for those new time series. Notification delay mean time is currently healthy, and no data loss has been observed. Engineering teams are continuing mitigation work and validating whether it clears the remaining delays. We will provide another update once validation is complete.
- identified Jul 11, 2026, 06:54 AM UTC
We continue to investigate delayed inclusion of newly created time series in detectors in US0. New time series may take up to 10 minutes to be included in detectors, which may delay detector evaluations for those time series. Notification delay mean time remains healthy, and no data loss has been observed. Engineering teams are performing a controlled rollout of affected backend components as part of ongoing mitigation work, and this is not expected to introduce additional customer impact. We will provide another update as validation progresses.
- identified Jul 11, 2026, 11:09 AM UTC
We continue to investigate delayed inclusion of newly created time series in detectors in US0. New time series may take up to 10 minutes to be included in detectors, which may delay detector evaluations for those time series. Notification delay mean time remains healthy, and no data loss has been observed. Engineering teams are performing a controlled rollout of affected backend components as part of ongoing mitigation work, and this is not expected to introduce additional customer impact. We will provide another update as validation progresses.
- identified Jul 11, 2026, 03:05 PM UTC
We continue to investigate delayed inclusion of newly created time series in detectors in US0. New time series may take up to 10 minutes to be included in detectors, which may delay detector evaluations for those time series. Notification delay mean time remains healthy, and no data loss has been observed. Engineering teams are performing a controlled rollout of affected backend components as part of ongoing mitigation work, and this is not expected to introduce additional customer impact. We will provide another update as validation progresses.
- resolved Jul 11, 2026, 06:09 PM UTC
This incident has been resolved.
Notice July 8, 2026 Small percentage of metric datapoints dropped in US0 –
Started Jul 08, 2026, 11:45 PM UTC· resolved Jul 08, 2026, 11:45 PM UTC
- resolved Jul 09, 2026, 02:36 AM UTC
Between 4:45p - 6:45p PDT a very small percentage of metric data points were being dropped. This issue has been resolved.
Minor July 8, 2026 Small Percentage of Datapoints Being Dropped in US0 2h 5m Datapoint Ingest
Started Jul 08, 2026, 09:47 PM UTC· resolved Jul 08, 2026, 11:52 PM UTC
- investigating Jul 08, 2026, 09:47 PM UTC
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.
- investigating Jul 08, 2026, 10:35 PM UTC
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.
- investigating Jul 08, 2026, 11:29 PM UTC
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.
- monitoring Jul 08, 2026, 11:33 PM UTC
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.
- resolved Jul 08, 2026, 11:52 PM UTC
This incident has been resolved.
Major July 8, 2026 Splunk Observability Synthetic Monitoring tests unavailable and APM Profiling unavailable in the user interface 1h 11m Splunk Synthetics Monitoring Interface, Splunk AlwaysOn Profiling Interface
Started Jul 08, 2026, 02:21 PM UTC· resolved Jul 08, 2026, 03:33 PM UTC
- investigating Jul 08, 2026, 02:21 PM UTC
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.
- investigating Jul 08, 2026, 02:43 PM UTC
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.
- investigating Jul 08, 2026, 03:05 PM UTC
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.
- resolved Jul 08, 2026, 03:33 PM UTC
This incident has been resolved.
Notice July 8, 2026 GCP Cloud Monitoring metrics not fetched in US0 –
Started Jul 08, 2026, 05:00 AM UTC· resolved Jul 08, 2026, 05:00 AM UTC
- resolved Jul 08, 2026, 10:51 AM UTC
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.
Major July 3, 2026 APM Trace Search and RUM Session Details Unavailable 2h Splunk APM Trace Data, Splunk RUM Session Details
Started Jul 03, 2026, 12:47 AM UTC· resolved Jul 03, 2026, 02:47 AM UTC
- investigating Jul 03, 2026, 12:47 AM UTC
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.
- investigating Jul 03, 2026, 01:10 AM UTC
We are continuing to investigate this issue.
- investigating Jul 03, 2026, 01:53 AM UTC
We are continuing to investigate this issue.
- identified Jul 03, 2026, 02:04 AM UTC
The issue has been identified and a fix is being implemented.
- resolved Jul 03, 2026, 02:47 AM UTC
This incident has been resolved.
Minor July 2, 2026 Detectors Delayed 1h 39m Splunk Observability Cloud Web Interface, Alerting
Started Jul 02, 2026, 08:55 PM UTC· resolved Jul 02, 2026, 10:35 PM UTC
- investigating Jul 02, 2026, 08:55 PM UTC
Customers may be experiencing delays in some detectors. Datapoint ingest is not affected. We are investigating and will provide an update shortly.
- identified Jul 02, 2026, 09:36 PM UTC
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.
- resolved Jul 02, 2026, 10:35 PM UTC
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.
Major July 2, 2026 Splunk APM Monitoring MetricSets delayed 2h 9m Splunk APM Interface, Splunk APM Monitoring MetricSets
Started Jul 02, 2026, 07:21 PM UTC· resolved Jul 02, 2026, 09:31 PM UTC
- investigating Jul 02, 2026, 07:21 PM UTC
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.
- investigating Jul 02, 2026, 08:16 PM UTC
We are continuing to investigate this issue.
- monitoring Jul 02, 2026, 08:44 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 02, 2026, 09:31 PM UTC
This incident has been resolved.
Minor July 1, 2026 A partial outage of Splunk APM Tag Spotlight –
Started Jul 01, 2026, 12:00 PM UTC· resolved Jul 01, 2026, 12:00 PM UTC
- resolved Jul 01, 2026, 02:18 PM UTC
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.
Minor June 25, 2026 Logs correlation experience from a APM TraceView page was broken. 17h 15m
Started Jun 25, 2026, 12:00 PM UTC· resolved Jun 26, 2026, 05:15 AM UTC
- resolved Jun 26, 2026, 07:36 AM UTC
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