Is SignalFx US0 down?

Last checked 9m ago
Current status
SignalFx US0 is up

No incidents right now.

Official status page: https://status.us0.signalfx.com · Polled every 5 minutes · 51 components tracked

SignalFx US0 is operational right now. Last checked 9m ago; the most recent incident resolved 1d ago.

Real-time SignalFx US0 status, recent outages, and incident history — pulled directly from SignalFx US0's official status page at https://status.us0.signalfx.com every 5 minutes. Pingoru tracks 51 SignalFx US0 services and has captured 26 incidents in the last 90 days (98.49% uptime). Get email, Slack, Discord, or webhook alerts the moment SignalFx US0 reports a new incident — free for 5 monitors, no credit card.

Users who monitor SignalFx US0 also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 6,000+ providers
SignalFx US0 uptime 98.49% uptime · past 90 days
Mon Wed Fri
MayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 46m
    Started Jul 31, 2026, 03:46 AM UTC · Resolved Jul 31, 2026, 04:32 AM UTC
    Splunk APM InterfaceSplunk APM Monitoring MetricSets
    Timeline · 4 updates
    • 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.

    Latest: The issue has been fixed.

  2. Resolved
    Started Jul 24, 2026, 11:00 AM UTC · Resolved Jul 24, 2026, 11:00 AM UTC
    Timeline · 1 update
    • 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.

    Latest: 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.

  3. Resolved 3h 39m
    Started Jul 15, 2026, 12:20 PM UTC · Resolved Jul 15, 2026, 04:00 PM UTC
    Splunk Observability Cloud APIAlerting
    Timeline · 4 updates
    • 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.

    Latest: This incident has been resolved.

  4. Resolved 3h 59m
    Started Jul 14, 2026, 03:45 PM UTC · Resolved Jul 14, 2026, 07:44 PM UTC
    Splunk Observability Cloud APIAlerting
    Timeline · 5 updates
    • investigating · Jul 14, 2026, 03:45 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 14, 2026, 04:49 PM UTC

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

    • identified · Jul 14, 2026, 05:52 PM UTC

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

    • monitoring · Jul 14, 2026, 07:07 PM UTC

      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.

    • resolved · Jul 14, 2026, 07:44 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved 1d 6h
    Started Jul 10, 2026, 12:03 PM UTC · Resolved Jul 11, 2026, 06:09 PM UTC
    Alerting
    Timeline · 20 updates
    • 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.

    Latest: This incident has been resolved.

See the full SignalFx US0 outage history

19 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse SignalFx US0 outage history →

Or sign up free to get alerts when SignalFx US0 breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 24 incidents View full outage history →