Splunk Observability Cloud US2 Outage History

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.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

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.

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.

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

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

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.

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.

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.

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.

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.

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.

Between 2026-01-23 at 3:30 AM PT and 2026-01-26 at 1:00 AM PT, metrics fetching from AWS Cloudwatch was degraded.

Jan 19, 12:10 PST Resolved - Engineering teams have identified the root cause and completed recovery actions that caused a degradation of service to the Hosts Infra Navigator View. Jan 19, 11:27 PST Update - We are continuing to investigate this issue. We have confirmed that the issue does not impact Datapoint Ingest at this time. Jan 19, 10:50 PST Investigating - We are currently investigating an issue that may result in the Hosts Infra Navigator View from loading.

Jan 14, 02:16 PST Resolved - This incident has been resolved. Jan 14, 02:12 PST Update - We are continuing to monitor for any further issues. Jan 14, 02:11 PST Monitoring - A fix has been implemented and we are monitoring the results. Jan 14, 02:02 PST Investigating - The service serving profiling ingest is unhealthy. This is resulting in new profiling data being dropped.

Oct 17, 18:37 PDT Resolved - This incident has been resolved. Oct 17, 17:31 PDT Monitoring - A fix has been implemented and we are monitoring the results. Oct 17, 15:56 PDT Update - We are continuing to work on a fix for this issue. Oct 17, 15:56 PDT Identified - The issue has been identified and a fix is being implemented.

APM Tag spotlight and other APM service-centric views within the UI were unavailable between approximately 1pm PDT and 11 pm PDT for customers without Profiling entitlements due to a system error. Data ingest was not impacted. The issue has been resolved.

Aug 20, 18:45 PDT Resolved - This incident has been resolved. Aug 20, 18:35 PDT Monitoring - A fix has been implemented and we are monitoring the results. Aug 20, 18:30 PDT Identified - The issue has been identified and a fix is being implemented. Aug 20, 01:30 PDT Investigating - We are investigating an elevated rate of errors occurring while interacting with the Splunk APM API. Trace data ingest is not impacted.

Aug 18, 15:34 PDT Resolved - Issue is resolved now and continue to monitor. Aug 18, 15:25 PDT Investigating - 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