Splunk Observability Cloud JP0 Outage History

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

We are continuing the investigation on the delays in processing Splunk Observability Synthetic Monitoring test results. Tests are still running, but metrics could be delayed until the issue is resolved. Splunk teams are engaged and investigating.

We are continuing the investigation on the delays in processing Splunk Observability Synthetic Monitoring test results. Tests are still running, but metrics could be delayed until the issue is resolved. Splunk teams are investigating and troubleshooting.

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.

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.

We are investigating a major outage of Splunk cloud involving logging in via Unified Identity. Ingest is not impacted at this time. We will provide an update as soon as possible. Splunk Log Observer may not be available for unified identity customers.

Our team is currently working to resolve an issue impacting Unified Identity services.

Investigation into the root cause of the Unified Identity issue is ongoing.

Customers may be experiencing errors while loading Data Management Page.

We are currently investigating an issue that may result in the Hosts Infra Navigator View from loading.

Users login with Splunk Unified Identity may have issues accessing Splunk Observability and Log Observer.

We are continuing to investigate this issue.

From the last half an hour we are seeing drop in datapoints because of issues in Datapoint ingest. We are investigating and will provide an update every 15 mins.

Splunk has identified a bug affecting all Unified Identity customers using Splunk Cloud version 9.3.2411.117 as their identity provider. Customers might be experiencing an inability to log in to Observability Cloud using the "Sign in via Splunk Cloud" workflow. The Splunk Cloud team is actively working on a solution, and the issue will be fully resolved once a patched version is released. The following workaround can be used by Customers using Unified Identity (without Centralized RBAC) until a patched version is released by the Splunk team 1. Customers using Unified Identity (without Centralized RBAC) can create a support case to have a set of users allow-listed for local login. 2. Once the users are allow-listed, the users will be able to login 3. After the patched version is released, the allowlist will be cleaned up There is no workaround for customers using Unified Identity (with Centralized RBAC) yet.

We are investigating an elevated rate of errors occurring while interacting with the Splunk APM API. Trace data ingest is not impacted.

A degradation in the performance of a key backend component of Splunk APM is causing both Troubleshooting and Monitoring MetricSets to be delayed by more than five minutes. No data is being dropped at this time but data for the APM Troubleshooting page and Tag Spotlight experience, as well as metrics created from traces and APM detectors are all delayed.

Synthetic Monitoring tests may experience issues, and runs may be missing or delayed until the issue is resolved. We will update the incident as we receive updated information.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

Customers using unified identity may experience intermittent failures while logging into Splunk Observability cloud web interface. Datapoint Ingest is not affected. We are investigating and will provide an update shortly.

We're experiencing failures for searches related to Log observer. We will provide an update as soon as possible.

A degradation in the performance of the Splunk APM trace processing pipeline is causing Troubleshooting MetricSets to be delayed by more than five minutes. As a result, the APM Troubleshooting experience, service maps and Tag Spotlight do not have access to the most recent data. The processing of metrics for Business Workflows, which also depends on this pipeline, are equally delayed. Trace data ingest is not impacted at this time; service-level and endpoint-level Monitoring MetricSets and the detectors built from them are also not impacted.

We are currently investigating this issue.