SignalFx US1 Outage History

SignalFx US1 is up right now

There were 9 SignalFx US1 outages since February 17, 2026 totaling 893h 15m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.us1.signalfx.com

Major April 25, 2026

RUM MMS Data Drop — Missing Chart & Dashboard Data

Detected by Pingoru
Apr 25, 2026, 05:01 PM UTC
Resolved
Apr 26, 2026, 12:55 AM UTC
Duration
7h 53m
Affected: Splunk RUM Monitoring MetricSets
Timeline · 6 updates
  1. investigating Apr 25, 2026, 05:01 PM UTC

    We are investigating an issue affecting Real User Monitoring (RUM) metrics across all realms. Customers may experience custom metric MTS quota limits being exceeded, resulting in metric data being dropped. RUM metric dimensions that were previously available may be missing.

  2. identified Apr 25, 2026, 05:02 PM UTC

    The issue affecting Real User Monitoring (RUM) metrics has been identified. The fix is currently being implemented. We are actively working to restore full service and will provide further updates as progress continues.

  3. identified Apr 25, 2026, 06:37 PM UTC

    We are continuing to work on the fix. We expect to have further updates within the next hour. We appreciate your patience as we work diligently to resolve this issue and restore full service.

  4. identified Apr 25, 2026, 10:26 PM UTC

    We are currently continuing to test the fix for the Real User Monitoring (RUM) metrics issue. We are thoroughly validating the mitigation to ensure it resolves the issue effectively and maintains system stability. We appreciate your ongoing patience and will provide further updates as testing progresses.

  5. identified Apr 25, 2026, 11:48 PM UTC

    We are currently continuing to test the fix for the Real User Monitoring (RUM) metrics issue. We will share an update once we have further information.

  6. resolved Apr 26, 2026, 12:55 AM UTC

    The outage impacting RUM MMS Data Drop has been resolved after internal engineering teams deployed a fix. All systems are operational and stable. Thank you for your patience and understanding.

Read the full incident report →

Minor April 17, 2026

Charts, dashboards and detectors loading is delayed

Detected by Pingoru
Apr 17, 2026, 04:20 PM UTC
Resolved
Apr 18, 2026, 04:02 AM UTC
Duration
11h 42m
Affected: Splunk Observability Cloud Web InterfaceSplunk Observability Cloud API
Timeline · 11 updates
  1. investigating Apr 17, 2026, 05:52 PM UTC

    Charts, dashboards and detectors may load slowly. Datapoint ingest is not affected. We are investigating and will provide an update shortly.

  2. identified Apr 17, 2026, 06:07 PM UTC

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

  3. identified Apr 17, 2026, 06:07 PM UTC

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

  4. monitoring Apr 17, 2026, 06:07 PM UTC

    We have identified the issue. The performance is improving. We will continue to monitor

  5. identified Apr 17, 2026, 06:15 PM UTC

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

  6. monitoring Apr 17, 2026, 06:44 PM UTC

    A fix has been implement and we are currently monitoring the environment.

  7. monitoring Apr 17, 2026, 07:49 PM UTC

    We are continuing to monitor the environment.

  8. identified Apr 17, 2026, 08:11 PM UTC

    We are moving the updates to an "Identified" status as we continue to address persistent performance issues affecting charts, dashboards, and detectors. While we are actively monitoring the environment and have implemented mitigation measures, some customers may still experience slow load times or intermittent failures. We are actively working to stabilize the environment and we will continue to provide updates as we make progress toward a full resolution.

  9. monitoring Apr 17, 2026, 09:10 PM UTC

    A fix has been implemented and we are currently monitoring the results to ensure system stability. We expect this monitoring period to last up to 4 hours. During this time, performance for charts, dashboards, and detectors should continue to improve. We will provide another update once we have confirmed that the environment has fully recovered.

  10. monitoring Apr 18, 2026, 01:40 AM UTC

    We are still under monitoring following the implementation of the fix to ensure stability. We will continue to track performance improvements for charts, dashboards, and detectors and will keep you updated as we confirm the environment has fully recovered.

  11. resolved Apr 18, 2026, 04:02 AM UTC

    This issue has been resolved. We have confirmed that system stability has been restored, and performance for charts, dashboards, and detectors has returned to normal levels. Thank you.

Read the full incident report →

Minor March 26, 2026

Splunk APM Monitoring MetricSets Delayed

Detected by Pingoru
Mar 26, 2026, 02:18 AM UTC
Resolved
Mar 26, 2026, 04:46 AM UTC
Duration
2h 27m
Affected: Splunk APM InterfaceSplunk APM Monitoring MetricSets
Timeline · 8 updates
  1. investigating Mar 26, 2026, 02:18 AM 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.

  2. investigating Mar 26, 2026, 02:20 AM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 26, 2026, 02:21 AM UTC

    We are continuing to investigate this issue.

  4. investigating Mar 26, 2026, 02:45 AM UTC

    We are continuing to investigate the performance degradation affecting Splunk APM Monitoring MetricSets. While trace data ingestion remains fully operational, users may experience delays of more than five minutes in dashboard, chart, and detector data. Our team is actively working to restore normal processing speeds, and we will provide further updates as more information becomes available

  5. investigating Mar 26, 2026, 03:18 AM UTC

    We are actively working to resolve the delay affecting trace monitoring metrics. While trace data ingestion remains unaffected, please note that dashboards, charts, and detectors may experience delays of over five minutes. We are working to restore normal latency and will provide further updates as they become available.

  6. monitoring Mar 26, 2026, 03:56 AM UTC

    Recovery efforts for trace monitoring metrics in the US1 region are progressing, with system lag steadily decreasing. We continue to monitor the service closely as it returns to normal performance levels. No data loss has occurred.

  7. monitoring Mar 26, 2026, 04:26 AM UTC

    We are continuing our recovery efforts for trace monitoring metrics in the US1 region. As system lag steadily decreases, we remain engaged in our standard monitoring procedures to ensure a full return to service. No data loss has occurred.

  8. resolved Mar 26, 2026, 04:46 AM UTC

    The issue impacting trace monitoring metrics in the US1 region is now resolved. All the APM monitoring sets are now fully operational and performing as expected. We confirm that no data was lost. Thank you for your patience.

Read the full incident report →

Minor March 25, 2026

Splunk APM Trace Data Ingestion Delayed

Detected by Pingoru
Mar 25, 2026, 07:04 PM UTC
Resolved
Mar 26, 2026, 01:54 AM UTC
Duration
6h 49m
Affected: Splunk APM Monitoring MetricSetsSplunk APM Troubleshooting MetricSetsSplunk APM Trace Data
Timeline · 9 updates
  1. investigating Mar 25, 2026, 07:04 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 fifteen 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.

  2. identified Mar 25, 2026, 08:23 PM UTC

    We are actively working to mitigate the performance degradation impacting the Splunk APM data ingestion pipeline. Efforts are underway to stabilize the environment and reduce delays in processing raw trace data. Customers may continue to experience delays in trace data availability, while MetricSets remain unaffected. We will provide further updates as mitigation progresses and system performance improves.

  3. identified Mar 25, 2026, 09:56 PM UTC

    We are continuing to work on mitigating the issue and stabilizing the environment. Customers may still experience delays of more than 15 minutes in trace data availability. In addition, Troubleshooting MetricSets (TMS) and Monitoring MetricSets (MMS) are also experiencing similar delays. We will provide further updates as progress continues.

  4. identified Mar 25, 2026, 11:16 PM UTC

    After applying some mitigations, they have not yielded the intended results. We continue to work on mitigating the issue and stabilizing the environment. Customers may still experience delays of more than 15 minutes in trace data availability. In addition, Troubleshooting MetricSets (TMS) and Monitoring MetricSets (MMS) are also experiencing similar delays. We will provide further updates as progress continues.

  5. identified Mar 25, 2026, 11:48 PM UTC

    We are actively mitigating the issue and monitoring as delays improve. Customers may still experience delays of over 15 minutes in trace data, as well as in Troubleshooting and Monitoring MetricSets. We will share further updates as progress is made.

  6. identified Mar 26, 2026, 12:09 AM UTC

    We are continuing to mitigate the issue and are seeing gradual improvement; customers may still experience delays of over 15 minutes in data processing and availability, and we will provide further updates as recovery progresses

  7. identified Mar 26, 2026, 12:28 AM UTC

    We are seeing gradual recovery as mitigation efforts take effect; customers may continue to experience delays in data processing and availability, though performance is steadily improving

  8. monitoring Mar 26, 2026, 12:46 AM UTC

    The latency issues have been resolved, and we are now monitoring the service to ensure continued stability. Thank you for your patience

  9. resolved Mar 26, 2026, 01:54 AM UTC

    The incident has been resolved, and data processing performance is now stable. Thank you for your patience.

Read the full incident report →

Minor March 24, 2026

New APM Data is Delayed

Detected by Pingoru
Mar 24, 2026, 01:54 AM UTC
Resolved
Mar 24, 2026, 03:02 AM UTC
Duration
1h 8m
Affected: Splunk APM IngestSplunk APM Trace DataSplunk APM Tag Spotlight
Timeline · 4 updates
  1. investigating Mar 24, 2026, 01:54 AM UTC

    We are currently investigating the issue. New APM Data is delayed by approximately 20 minutes. There is no data loss.

  2. investigating Mar 24, 2026, 02:37 AM UTC

    Investigation is in progress. Our team is working on mitigation steps and will provide further update as soon as possible

  3. investigating Mar 24, 2026, 02:50 AM UTC

    Mitigation steps are in progress, and the situation is improving. We are continuing to monitor and will provide further updates as soon as possible

  4. resolved Mar 24, 2026, 03:02 AM UTC

    The issue has been resolved and services have returned to normal operation. Thank you for your patience.

Read the full incident report →

Minor March 23, 2026

Synthetics tests running from Bahrain may not run on schedule

Detected by Pingoru
Mar 23, 2026, 11:28 PM UTC
Resolved
Apr 25, 2026, 02:55 AM UTC
Duration
32d 3h
Affected: Splunk Synthetics Monitoring Runners
Timeline · 4 updates
  1. identified Mar 23, 2026, 11:28 PM UTC

    The issue has been identified and is due to a Cloud Provider outage in the Bahrain region.

  2. identified Mar 24, 2026, 12:57 AM UTC

    The issue has been identified as an outage affecting the Bahrain region due to a Cloud Provider outage. We recommend that users temporarily run their Synthetic Monitoring tests from an alternative location while this issue is being resolved by the Cloud Provider.

  3. identified Mar 24, 2026, 06:19 PM UTC

    The issue has been identified as a regional cloud provider outage that is impacting our ability to maintain Synthetics testing in specific areas. Due to the uncertainty regarding the resolution timeline for this issue, we have made the decision to temporarily remove the following locations from our Synthetics testing network: Bahrain Muscat UAE We recommend reviewing your current test configurations and selecting alternative testing locations if necessary to ensure continued coverage. Our engineering team is monitoring the situation closely. We will provide further updates as more information becomes available from the cloud provider. We apologize for any inconvenience this may cause and appreciate your patience as we work to maintain the reliability of our services.

  4. resolved Apr 25, 2026, 02:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 2, 2026

Potential Cloud Integration Issues In UAE Region

Detected by Pingoru
Mar 02, 2026, 08:32 AM UTC
Resolved
Mar 05, 2026, 07:24 PM UTC
Duration
3d 10h
Affected: Splunk Cloud Metric SyncerSplunk CloudWatch Metric Streams
Timeline · 5 updates
  1. investigating Mar 02, 2026, 08:32 AM UTC

    Cisco is aware of an ongoing cloud service provider outage in the Middle East affecting multiple cloud offers and services. As a result, O11y customers ingesting metrics and/or metadata from impacted regions may experience significant delays and/or interruptions in data delivery. Customers who do not rely on metrics or metadata from these regions are not affected. We will continue to closely monitor this issue as it unfolds.

  2. monitoring Mar 02, 2026, 08:33 AM UTC

    Cisco is aware of an ongoing cloud service provider outage in the Middle East affecting multiple cloud offers and services. As a result, O11y customers ingesting metrics and/or metadata from impacted regions may experience significant delays and/or interruptions in data delivery. Customers who do not rely on metrics or metadata from these regions are not affected. We will continue to closely monitor this issue as it unfolds.

  3. monitoring Mar 02, 2026, 08:22 PM UTC

    Cisco is aware of an ongoing cloud service provider outage in the Middle East affecting multiple cloud offers and services. As a result, O11y customers ingesting metrics and/or metadata from impacted regions may experience significant delays and/or interruptions in data delivery. Customers who do not rely on metrics or metadata from these regions are not affected. We will continue to closely monitor this issue as it unfolds.

  4. monitoring Mar 03, 2026, 05:15 PM UTC

    Cisco is aware of an ongoing cloud service provider outage in the Middle East affecting multiple cloud offers and services. As a result, O11y customers ingesting metrics and/or metadata from impacted regions may experience significant delays and/or interruptions in data delivery. Customers who do not rely on metrics or metadata from these regions are not affected. We will continue to closely monitor this issue as it unfolds.

  5. resolved Mar 05, 2026, 07:24 PM UTC

    Monitoring over the past several days has not identified any impact to Splunk Observability Cloud services related to the previously reported cloud service provider disruption in the Middle East. Splunk Observability Cloud services continue to operate normally. We will continue to monitor the situation and will notify customers if conditions change.

Read the full incident report →

Minor February 26, 2026

Dashboard and Detectors are not loading

Detected by Pingoru
Feb 26, 2026, 03:00 PM UTC
Resolved
Feb 26, 2026, 08:25 PM UTC
Duration
5h 25m
Affected: Datapoint IngestSplunk Synthetics Monitoring Interface
Timeline · 8 updates
  1. investigating Feb 26, 2026, 03:00 PM UTC

    We are currently investigating this issue.

  2. investigating Feb 26, 2026, 04:05 PM UTC

    We are currently investigating an issue causing failures in analytics jobs and impacting chart and detector functionality in the UI. Customers may experience degraded performance or data loading issues. Team is actively working to identify mitigation to restore full functionality. We will provide further updates as more information becomes available.

  3. identified Feb 26, 2026, 05:00 PM UTC

    We have identified the cause of the issue impacting analytics job processing and UI functionality. Issue was triggered following a ZooKeeper master node restart during scheduled maintenance, which led to service instability and job failures. Recovery actions are in progress, including restarting affected services and stabilizing the environment. Customers may continue to experience degraded performance or data loading issues while mitigation steps are being completed. We will provide further updates as restoration progresses.

  4. identified Feb 26, 2026, 06:13 PM UTC

    We are continuing to make progress restoring analytics job processing and UI functionality. Affected services have been restarted. While recovery is progressing, customers may still experience data delays due to backlog processing. Team is actively working on expediting recovery progress.

  5. identified Feb 26, 2026, 07:01 PM UTC

    We are continuing restoring analytics job processing and overall UI functionality. The majority of affected services have been successfully restarted, and rolling restarts for remaining components are currently underway. Customers may continue to experience data delays as analytics and detector services process backlogs. We will provide additional updates as stability and performance are fully restored.

  6. monitoring Feb 26, 2026, 07:44 PM UTC

    Recovery is complete. Charts and detectors are now loading with 100% successful displayed data. The team are actively monitoring the situation to ensure of no further issues.

  7. monitoring Feb 26, 2026, 08:25 PM UTC

    We are continuing to monitor for any further issues.

  8. resolved Feb 26, 2026, 08:25 PM UTC

    We have completed the remediation actions and have successfully resolved the incident. At this time, no further action is required of you.

Read the full incident report →

Major February 17, 2026

Data Management Page is not loading

Detected by Pingoru
Feb 17, 2026, 06:25 PM UTC
Resolved
Feb 17, 2026, 09:56 PM UTC
Duration
3h 30m
Affected: Splunk Observability Cloud Web Interface
Timeline · 7 updates
  1. investigating Feb 17, 2026, 06:25 PM UTC

    Customers may be experiencing errors while loading Data Management Page.

  2. identified Feb 17, 2026, 06:50 PM UTC

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

  3. identified Feb 17, 2026, 07:28 PM UTC

    Our teams are actively working to restore services. Some customers may be seeing improvement at this time. We are committed to resolving the issue as quickly as possible and will provide updates as progress is made.

  4. identified Feb 17, 2026, 08:05 PM UTC

    Restoration is still in progress. Retrying to load the Data Management Page should yield positive results for some customers. Our teams continue to work diligently to resolve the issue and will provide further updates as progress is made.

  5. identified Feb 17, 2026, 08:41 PM UTC

    Restoration is mostly complete. Most customer attempts to load the Data Management Page should be successful. Our teams continue to monitor the situation and appreciate your patience as we finalize the resolution. Further updates will be provided if necessary.

  6. monitoring Feb 17, 2026, 09:50 PM UTC

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

  7. resolved Feb 17, 2026, 09:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track SignalFx US1 downtime and outages?

Pingoru polls SignalFx US1's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when SignalFx US1 reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track SignalFx US1 alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring SignalFx US1 for free

5 free monitors · No credit card required