https://approjects-vendor-status-watch.static.hf.space/v/signalfx-us1.htmlIncidents from SignalFx US1's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/338zhkhpkyscsignalfx-us1:2026-09-15T07:41:40.826-07:00Tue, 15 Sep 2026 14:41:40 +0000The system has recovered and we ingesting archived data with no delay.https://stspg.io/wxp3xxnfby4gsignalfx-us1:2026-09-12T09:32:27.714-07:00Sat, 12 Sep 2026 16:32:27 +0000The issue has been resolved, and datapoint ingestion is operating normally. We have confirmed that the system remains stable following remediation. This incident is now resolved.https://stspg.io/vyypzjnhhxgfsignalfx-us1:2026-08-28T11:01:03.159-07:00Fri, 28 Aug 2026 18:01:03 +0000Monitoring phase complete. The issue has been resolved.https://stspg.io/cqqz8ldwldtssignalfx-us1:2026-08-25T11:44:49.798-07:00Tue, 25 Aug 2026 18:44:49 +0000This incident has been resolved.https://stspg.io/gvww271x0gmmsignalfx-us1:2026-08-01T07:35:56.120-07:00Sat, 01 Aug 2026 14:35:56 +0000The notification delivery delays have been fully resolved. All queued notifications have been processed and the system is now operating normally.https://stspg.io/zfrcyhpbjn8csignalfx-us1:2026-07-30T19:51:03.059-07:00Fri, 31 Jul 2026 02:51:03 +0000This incident has been resolved.https://stspg.io/ns5lymnld8hysignalfx-us1:2026-07-24T14:00:00.000-07:00Fri, 24 Jul 2026 21:00:00 +0000Datapoint ingest for new or reactivated metric time series was affected between 2:28 PM PST to 2:47 PM PST. There was partial data loss for new metric time series during that time period. This situation is now recovered.https://stspg.io/mslznlnqsrvpsignalfx-us1:2026-07-22T11:01:24.000-07:00Wed, 22 Jul 2026 18:01:24 +0000Datapoint ingest for new metric time series was affected between 10:37 AM PST and 10:39 AM PST. There was partial data loss for new metric time series during that time period. This situation is now recovered.https://stspg.io/pv8h2byhfqcysignalfx-us1:2026-07-14T04:25:05.333-07:00Tue, 14 Jul 2026 11:25:05 +0000This incident has been resolved. Please note that the Splunk Observability Cloud API was also affected during this incident.https://stspg.io/tpc6zbj6c41ysignalfx-us1:2026-07-07T22:00:00.000-07:00Wed, 08 Jul 2026 05:00:00 +0000Between 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.https://stspg.io/hgf3cs78jk8ysignalfx-us1:2026-07-04T10:07:07.522-07:00Sat, 04 Jul 2026 17:07:07 +0000The issue causing delays in newly created metric time series has been resolved. Metric time series creation is operating normally. Datapoint ingestion for existing time series was not affected.https://stspg.io/n1x7hdt213zysignalfx-us1:2026-07-01T08:08:56.906-07:00Wed, 01 Jul 2026 15:08:56 +0000We have confirmed that the issue affecting Tag Spotlight has been resolved. Customers may have experienced limited functionality within Tag Spotlight beginning at approximately 4:30 PM PT on June 30. Full functionality was restored at 7:20 AM PT on July 1.https://stspg.io/p18s6jszt924signalfx-us1:2026-06-25T05:00:00.000-07:00Thu, 25 Jun 2026 12:00:00 +0000Due 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, 2026https://stspg.io/kw2pc5lnbd4vsignalfx-us1:2026-06-11T02:00:00.000-07:00Thu, 11 Jun 2026 09:00:00 +0000Rum API Endpoints were not available for one of our IPs, resulting in degraded service or a partial outage at first, and possibly a complete outage towards the end. This issue occurred from 4:22pm PST to 4:57pm PSThttps://stspg.io/cgw5yydczmrbsignalfx-us1:2026-06-03T15:49:56.354-07:00Wed, 03 Jun 2026 22:49:56 +0000Our engineering team has confirmed that all the services recovered as of 4:55 PM PDT and remained stable during monitoring. This incident is now resolved.https://stspg.io/vwpk2hm0pgd5signalfx-us1:2026-06-02T05:50:46.927-07:00Tue, 02 Jun 2026 12:50:46 +0000We have identified and remediated an issue affecting synthetic test result ingestion for a subset of customers. We apologize for any inconvenience this may have caused and thank you for your patience. Time range of impact: June 1 20:00 UTC - June 2 15:30 UTChttps://stspg.io/gvs3ptgc6crcsignalfx-us1:2026-05-28T22:24:09.218-07:00Fri, 29 May 2026 05:24:09 +0000This Incident has been resolved.https://stspg.io/xcl82kj7shd4signalfx-us1:2026-05-11T15:40:16.000-07:00Mon, 11 May 2026 22:40:16 +0000This incident has been resolved. We have since confirmed that only AWS CloudWatch metrics were impacted during this incident. Azure and GCP metrics were not impacted.https://stspg.io/39zslyrngbj5signalfx-us1:2026-05-07T18:15:31.000-07:00Fri, 08 May 2026 01:15:31 +0000This incident has been resolved.https://stspg.io/1z4vnnr1wpb1signalfx-us1:2026-05-06T06:00:54.000-07:00Wed, 06 May 2026 13:00:54 +0000This incident has been resolved.https://stspg.io/r1wf8qmz261nsignalfx-us1:2026-04-25T10:01:46.351-07:00Sat, 25 Apr 2026 17:01:46 +0000The 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.https://stspg.io/5llnpsb2yf2hsignalfx-us1:2026-04-24T18:03:16.631-07:00Sat, 25 Apr 2026 01:03:16 +0000The issue affecting Real User Monitoring (RUM) custom charts and dashboards across multiple realms has been resolved. The fix has been deployed, and data is now flowing normally.https://stspg.io/bs463yd8px9bsignalfx-us1:2026-04-17T09:20:08.000-07:00Fri, 17 Apr 2026 16:20:08 +0000This 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.https://stspg.io/pdl64cx8120zsignalfx-us1:2026-03-25T19:18:24.024-07:00Thu, 26 Mar 2026 02:18:24 +0000The 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.https://stspg.io/bcb63ltwg3g6signalfx-us1:2026-03-25T12:04:33.962-07:00Wed, 25 Mar 2026 19:04:33 +0000The incident has been resolved, and data processing performance is now stable. Thank you for your patience.https://stspg.io/910p808dj3h3signalfx-us1:2026-03-23T18:54:11.328-07:00Tue, 24 Mar 2026 01:54:11 +0000The issue has been resolved and services have returned to normal operation. Thank you for your patience.https://stspg.io/8vjy8ctc43z1signalfx-us1:2026-03-23T16:28:59.000-07:00Mon, 23 Mar 2026 23:28:59 +0000This incident has been resolved.https://stspg.io/0j0268j3l3wqsignalfx-us1:2026-03-02T00:32:46.918-08:00Mon, 02 Mar 2026 08:32:46 +0000Monitoring 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.https://stspg.io/2bbfxc25wjsfsignalfx-us1:2026-02-26T07:00:37.399-08:00Thu, 26 Feb 2026 15:00:37 +0000We have completed the remediation actions and have successfully resolved the incident.  At this time, no further action is required of you.https://stspg.io/8ljzzlcgfwf2signalfx-us1:2026-02-17T10:25:43.179-08:00Tue, 17 Feb 2026 18:25:43 +0000This incident has been resolved.