Signalfx outage history

We are investigating an issue with the AWS CloudWatch integration. Some customers may see missing or outdated resource tags on AWS metrics, and metric stream configuration changes may not be applied. Metric ingestion is not impacted. We will provide an update as soon as more information is available.

We have identified that the degraded AWS CloudWatch integration is caused by an ongoing AWS disruption in the me-central-1 (UAE) region, including AWS CloudWatch and the Resource Groups Tagging API. Customers with AWS resources in this region may see missing or outdated resource tags on AWS metrics, and metric stream configuration changes may not be applied. Metric ingestion is not impacted. AWS has not provided a recovery timeline and recommends migrating to another region.

Splunk has confirmed that the degraded AWS CloudWatch integration in the me-central-1 (UAE) region is caused by an ongoing AWS regional disruption outside of Splunk's control. AWS has not provided a recovery timeline and recommends migrating affected resources to another region. Metric ingestion is not impacted. We are identifying affected customers and will reach out individually to discuss next steps. If you have immediate concerns, please contact your account team.

APM UI for a subset of customers may be have degraded experience. We are investigating and will provide an update shortly.

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.

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

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.

Some of the customer are seeing login failures due to certificate errors. Customers that are already logged are not impacted. The issue 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), July 24th, 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.

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.

Customer impact began around 7:00 AM PDT. We have identified a fix, but a full recovery could take several hours

We are continuing to work on a fix for this issue. A full recovery could take several hours

A fix has been implemented and we are monitoring the results as backlog recovers. Alert states and event time series in the UI may be delayed while the backlog recovers.

This incident has been resolved.

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.

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

We are continuing to monitor for any further issues.

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.

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.

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.

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.

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.

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.

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.

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.

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.