Splunk Observability Cloud US2 Outage History

Splunk Observability Cloud US2 is up right now

Pingoru has recorded 62 incidents for Splunk Observability Cloud US2: 38 in the last 12 months and 12 in the last 90 days.

Source: status.us2.signalfx.com

62incidents recorded
38last 12 months
12last 90 days
43 hourstypical duration
Incidents per month
048AprMayJunJulAugSepOct2
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct1%
Pingoru began tracking Splunk Observability Cloud US2 in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20267190 of 720 (26%)
May 2026111 of 744 (1%)
June 2026221 of 720 (3%)
July 2026610 of 744 (1%)
August 2026629 of 744 (4%)
September 202610 of 720 (0%)
October 202623 of 542 (1%)

Incidents, newest first

Minor October 12, 2026 Reactivated MTS may be delayed in charts and detectors 2h 19m Datapoint Ingest

Started Oct 12, 2026, 09:33 PM UTC· resolved Oct 12, 2026, 11:53 PM UTC

  1. identified Oct 12, 2026, 09:33 PM UTC

    Reactivated MTS may be delayed showing up in charts and detectors

  2. identified Oct 12, 2026, 10:03 PM UTC

    We are continuing to work on the recovery of the system.

  3. identified Oct 12, 2026, 10:33 PM UTC

    We are continuing to work on the recovery of the system.

  4. identified Oct 12, 2026, 11:03 PM UTC

    We are continuing to work on the recovery of the system.

  5. identified Oct 12, 2026, 11:33 PM UTC

    We are continuing to work on the recovery of the system.

  6. resolved Oct 12, 2026, 11:53 PM UTC

    The recovery of the system has completed.

Read the full incident report →

Minor October 3, 2026 Splunk Observability Synthetic Metric may be missing 49m Splunk Synthetics Monitoring Results processing

Started Oct 03, 2026, 02:20 AM UTC· resolved Oct 03, 2026, 03:09 AM UTC

  1. investigating Oct 03, 2026, 02:46 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.

  2. investigating Oct 03, 2026, 02:47 AM UTC

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

  3. identified Oct 03, 2026, 02:54 AM UTC

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

  4. monitoring Oct 03, 2026, 02:54 AM UTC

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

  5. monitoring Oct 03, 2026, 02:57 AM UTC

    We are continuing to monitor for any further issues.

  6. resolved Oct 03, 2026, 03:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 18, 2026 Potential Login Issues –

Started Sep 18, 2026, 03:39 PM UTC· resolved Sep 18, 2026, 03:39 PM UTC

  1. resolved Sep 18, 2026, 03:39 PM UTC

    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.

Read the full incident report →

Notice August 21, 2026 Notification Delay Observed 42m

Started Aug 21, 2026, 08:00 PM UTC· resolved Aug 21, 2026, 08:42 PM UTC

  1. resolved Aug 21, 2026, 09:23 PM UTC

    From 8/21/2026 1:00 PM PDT, customers might experience delay of their notification delivery (up to an hour). No data was loss. The issue was fully mitigated on 08/21/2026 1:42 PM PDT.

Read the full incident report →

Critical August 20, 2026 Datapoints Being Dropped on US2 3h 26m Datapoint Ingest

Started Aug 20, 2026, 03:19 PM UTC· resolved Aug 20, 2026, 06:45 PM UTC

  1. investigating Aug 20, 2026, 03:19 PM UTC

    Datapoint ingest is affected and we are dropping datapoints. This started at around 08/20/2026 8:01am PST. We are investigating and will provide an update every 15 mins.

  2. investigating Aug 20, 2026, 03:46 PM UTC

    We are continuing to investigate this issue.

  3. investigating Aug 20, 2026, 04:10 PM UTC

    We have identified small amount of Datapoint ingested is being dropped. It has been verified that Span is being dropped for a hour. We are continuing to investigate this issue.

  4. investigating Aug 20, 2026, 04:40 PM UTC

    We are continuing to investigate this issue.

  5. investigating Aug 20, 2026, 04:52 PM UTC

    One of our vendors is reporting an outage, which is related to the ongoing issue. We are currently working with the vendor to resolve the issue. We are continuing to investigate this issue.

  6. investigating Aug 20, 2026, 05:08 PM UTC

    One of our vendors is reporting an outage, which is related to the ongoing issue. We are currently working with the vendor to resolve the issue. We are continuing to investigate this issue.

  7. identified Aug 20, 2026, 05:14 PM UTC

    Starting to see recovery in progress.

  8. monitoring Aug 20, 2026, 05:37 PM UTC

    Recovery in progress. We are continuing to monitor

  9. monitoring Aug 20, 2026, 05:53 PM UTC

    Recovery in progress. We are continuing to monitor

  10. monitoring Aug 20, 2026, 06:09 PM UTC

    Recovery in progress. We are continuing to monitor

  11. monitoring Aug 20, 2026, 06:24 PM UTC

    Recovery in progress. We are continuing to monitor

  12. monitoring Aug 20, 2026, 06:37 PM UTC

    We are continuing to monitor for any further issues.

  13. monitoring Aug 20, 2026, 06:38 PM UTC

    We are continuing to monitor for any further issues.

  14. monitoring Aug 20, 2026, 06:40 PM UTC

    Recovery in progress. We are continuing to monitor

  15. resolved Aug 20, 2026, 06:45 PM UTC

    Recovery completed. Datapoint ingestion is now working as expected.

Read the full incident report →

Notice August 17, 2026 Splunk Observability Synthetic Monitoring Partial Run Result Data Loss 20h 47m

Started Aug 17, 2026, 11:00 PM UTC· resolved Aug 18, 2026, 07:47 PM UTC

  1. resolved Aug 21, 2026, 08:32 PM UTC

    From 08/17/2026 4:00 PM PDT, Splunk Observability Synthetic Monitoring partial run result data loss was observed. Customers might see occasional gaps in their listed run results. Full metric data was still available. Detectors were not impacted. The issue was fully mitigated on 08/21/2026 12:47PM PDT.

Read the full incident report →

Major August 6, 2026 Charts are not Loading for customers 59m Splunk Observability Cloud Web Interface

Started Aug 06, 2026, 02:45 AM UTC· resolved Aug 06, 2026, 03:44 AM UTC

  1. investigating Aug 06, 2026, 02:45 AM UTC

    Some of Charts may not be loading. Datapoint ingest is not affected. We are investigating and will provide an update shortly.

  2. monitoring Aug 06, 2026, 03:31 AM UTC

    Fix has been implemented for the issue affecting some Splunk Observability Cloud charts in the US2 realm. We are continuing to monitor service stability and will provide another update once validation is complete.

  3. resolved Aug 06, 2026, 03:44 AM UTC

    This incident has been resolved. Thank you for your patience.

Read the full incident report →

Minor August 5, 2026 Splunk APM Trace Data Ingestion Delayed 1h 42m Splunk APM Trace Data

Started Aug 05, 2026, 01:53 AM UTC· resolved Aug 05, 2026, 03:35 AM UTC

  1. investigating Aug 05, 2026, 01:53 AM 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.

  2. investigating Aug 05, 2026, 02:50 AM UTC

    We are continuing to investigate the degradation in the Splunk APM data ingestion pipeline. Processing and storage of raw trace data remains delayed by more than five minutes, so the most recent data may not be available in trace search results. No data is being lost at this time, and MetricSets are not impacted. Teams are working to restore normal processing and reduce ingestion delays.

  3. resolved Aug 05, 2026, 03:35 AM UTC

    The degradation in the Splunk APM data ingestion pipeline has been mitigated and is now resolved. Processing and storage of raw trace data has recovered, and recent data is available in trace search results. No data was lost, and MetricSets were not impacted. Thank you for your patience.

Read the full incident report →

Minor July 31, 2026 Splunk APM Monitoring MetricSets Delayed 1h 33m Splunk APM Monitoring MetricSets

Started Jul 31, 2026, 02:49 AM UTC· resolved Jul 31, 2026, 04:22 AM UTC

  1. investigating Jul 31, 2026, 02:49 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.

Read the full incident report →

Major July 30, 2026 The AI Assistant is intermittently returning errors for some queries. 37m Splunk Observability Cloud API

Started Jul 30, 2026, 10:45 PM UTC· resolved Jul 30, 2026, 11:22 PM UTC

  1. investigating Jul 30, 2026, 10:45 PM UTC

    We are currently investigating this issue.

  2. resolved Jul 30, 2026, 11:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 30, 2026 Splunk Observability MCP Tools are not loading in US2 realm 1h 6m Splunk Observability Cloud API

Started Jul 30, 2026, 10:18 PM UTC· resolved Jul 30, 2026, 11:24 PM UTC

  1. investigating Jul 30, 2026, 10:18 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.

  2. investigating Jul 30, 2026, 11:01 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jul 30, 2026, 11:06 PM UTC

    Identified the root cause, continuing to work on it.

  4. monitoring Jul 30, 2026, 11:16 PM UTC

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

  5. resolved Jul 30, 2026, 11:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 16, 2026 US2: Delayed visibility of newly created MTS in charts and dashboards 6h 55m Splunk Observability Cloud Web Interface, Splunk APM Monitoring MetricSets, Alerting, Splunk RUM Monitoring MetricSets

Started Jul 16, 2026, 06:54 AM UTC· resolved Jul 16, 2026, 01:50 PM UTC

  1. investigating Jul 16, 2026, 06:54 AM UTC

    We are currently investigating an issue where newly created MTS are taking longer than usual to appear in charts for customers in the US2 region. There is currently no data loss reported.

  2. investigating Jul 16, 2026, 07:29 AM UTC

    The MTS issues has been resolved by the Splunk observability teams. Ther should not be further delays in the charts.

  3. resolved Jul 16, 2026, 01:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 8, 2026 GCP Cloud Monitoring metrics not fetched in US2 –

Started Jul 08, 2026, 05:00 AM UTC· resolved Jul 08, 2026, 05:00 AM UTC

  1. resolved Jul 08, 2026, 10:53 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.

Read the full incident report →

Notice July 1, 2026 A partial outage of Splunk APM Tag Spotlight – Splunk APM Tag Spotlight

Started Jul 01, 2026, 03:09 PM UTC· resolved Jul 01, 2026, 03:09 PM UTC

  1. resolved Jul 01, 2026, 03:09 PM UTC

    We 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.

Read the full incident report →

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

  1. resolved Jun 26, 2026, 07:38 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

Read the full incident report →

Minor June 2, 2026 Splunk Observability Synthetic Monitoring Results Processing delayed 3h 57m Splunk Synthetics Monitoring Results processing

Started Jun 02, 2026, 12:51 PM UTC· resolved Jun 02, 2026, 04:49 PM UTC

  1. investigating Jun 02, 2026, 12:51 PM UTC

    We are investigating delays in processing Splunk Observability Synthetic Monitoring test results for a small subset of customers. Tests are still running, but metrics may be delayed until the issue is resolved.

  2. resolved Jun 02, 2026, 04:49 PM UTC

    We 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 17:30 UTC - June 2 14:30 UTC

Read the full incident report →

Major May 12, 2026 [US2] Azure Monitor and GCP Cloud Monitoring metrics not fetched 11h Cloud Integrations

Started May 12, 2026, 10:30 PM UTC· resolved May 13, 2026, 09:30 AM UTC

  1. investigating May 13, 2026, 10:08 AM UTC

    A degradation of the Splunk O11y Cloud ingest path caused ~5% of Azure Monitor and GCP Cloud Monitoring metrics to not be fetched. AWS Cloudwatch Metrics were not impacted.

  2. investigating May 13, 2026, 10:08 AM UTC

    This incident has been resolved. We have since confirmed that Azure Monitor and GCP Cloud Monitoring metrics were impacted during this incident. AWS Cloud Monitoring metrics were not impacted.

  3. resolved May 13, 2026, 10:15 AM UTC

    This incident has been resolved. We have since confirmed that Azure Monitor and GCP Cloud Monitoring metrics were impacted during this incident. AWS Cloud Monitoring metrics were not impacted.

Read the full incident report →

Minor April 29, 2026 Organizations Stuck in Playground Mode –

Started Apr 29, 2026, 10:20 PM UTC· resolved Apr 29, 2026, 10:20 PM UTC

  1. resolved May 01, 2026, 11:46 PM UTC

    Users may have observed a modified Playground UI (hidden org selector, added header, and an Exit Playground button with unexpected org‑switch behavior). No features were affected and no user experience was degraded. The issue was identified and fully mitigated by 16:49 PDT.

Read the full incident report →

Critical April 25, 2026 RUM MMS Data Drop — Missing Chart & Dashboard Data 9h 15m Splunk RUM Monitoring MetricSets

Started Apr 25, 2026, 03:40 PM UTC· resolved Apr 26, 2026, 12:55 AM UTC

  1. investigating Apr 25, 2026, 03:40 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. investigating Apr 25, 2026, 04:28 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:38 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:27 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 20, 2026 Dropping a subset of metrics in us2 –

Started Apr 20, 2026, 06:09 PM UTC· resolved Apr 20, 2026, 06:09 PM UTC

  1. monitoring Apr 20, 2026, 03:55 PM UTC

    Apr 20, 07:30 PDT Investigating - We are currently dropping a subset of metrics. We are currently working on identifying the root cause.

Read the full incident report →

Minor April 14, 2026 Splunk APM New Data is Delayed –

Started Apr 14, 2026, 02:01 AM UTC· resolved Apr 14, 2026, 02:01 AM UTC

  1. resolved Apr 14, 2026, 02:01 AM UTC

    Apr 13, 19:01 PDT Resolved - This incident has been resolved. Apr 13, 18:58 PDT Monitoring - A fix has been implemented and we are monitoring the results. Apr 13, 18:57 PDT Update - Mitigation steps are in progress, and the situation is improving. We are continuing to monitor and will provide further updates as soon as possible. Apr 13, 18:52 PDT Update - Mitigation steps are in progress. We are continuing to monitor and will provide further updates as soon as possible Apr 13, 18:29 PDT Update - Mitigation steps are in progress. We are continuing to monitor and will provide further updates as soon as possible Apr 13, 18:06 PDT Update - Investigation is in progress. Our team is working on mitigation steps and will provide further update as soon as possible. Apr 13, 17:27 PDT Investigating - We are currently investigating the issue. APM New Data is delayed by approximately 40 minutes. There is no data loss.

Read the full incident report →

Minor March 25, 2026 Synthetics tests running from Bahrain may not run on schedule 27d 22h

Started Mar 25, 2026, 05:41 AM UTC· resolved Apr 22, 2026, 04:32 AM UTC

  1. monitoring Mar 25, 2026, 05:41 AM UTC

    Mar 24, 11:20 PDT Update - 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. Mar 23, 17:57 PDT Update - 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. Mar 23, 16:29 PDT Identified - The issue has been identified and is due to a Cloud Provider outage in the Bahrain region.

Read the full incident report →

Minor March 17, 2026 Trace analyzer screen is intermittently unavailable –

Started Mar 17, 2026, 11:51 PM UTC· resolved Mar 17, 2026, 11:51 PM UTC

  1. resolved Mar 17, 2026, 11:51 PM UTC

    Mar 17, 16:51 PDT Resolved - The issue with APM Trace Analyzer page functionality is fully recovered. Mar 17, 15:45 PDT Monitoring - The issue with APM Trace Analyzer page functionality has recovered, and engineering teams are monitoring to ensure continued health of the system. Mar 17, 15:14 PDT Update - We are currently investigating an issue with a subset of APM functionality called trace analyzer which allows customers to browse traces for filtering and sorting, function is degraded. Mar 17, 14:15 PDT Investigating - We are currently investigating this issue.

Read the full incident report →

Minor March 5, 2026 Potential Cloud Integration Issues In UAE Region –

Started Mar 05, 2026, 07:24 PM UTC· resolved Mar 05, 2026, 07:24 PM UTC

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

    Mar 5, 11:24 PST Resolved - 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. Mar 3, 09:15 PST Update - 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. Mar 2, 12:24 PST Update - 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. Mar 2, 00:34 PST Monitoring - 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.

Read the full incident report →

Minor February 28, 2026 Splunk Synthetics Google Chrome Upgrade –

Started Feb 28, 2026, 08:00 AM UTC· resolved Feb 28, 2026, 08:00 AM UTC

  1. resolved Feb 28, 2026, 08:00 AM UTC

    Feb 28, 00:00 PST Completed - The scheduled maintenance has been completed. Feb 9, 00:00 PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb 2, 09:45 PST Scheduled - Splunk Synthetic Monitoring will begin updating Google Chrome to version 142 for Browser tests on Monday, February 9th at 12:00 AM PT. We periodically auto-update to newer versions of Google Chrome when available. Due to differences between browser versions, test behavior or timings can sometimes change and may require updates to your test steps. This rollout will be done gradually over two weeks, after which a new runner version for Private Location customers will be made available.

Read the full incident report →