Is Splunk Observability Cloud US2 Down Right Now? Check if there is a current outage ongoing.

This incident has been resolved.

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

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

Charts and metadata API requests for a subset of customers may not be loading. Datapoint ingest is not affected. We are investigating and will provide an update shortly.

Charts and metadata API requests for a subset of customers may not be loading. Datapoint ingest is not affected. We are investigating and will provide an update shortly.

Between 7:40am and 8:10am PT users may have experienced errors while loading the UI or accessing metric metadata APIs. Data ingest and alerting were not impacted. The issue has since been resolved.

Between 7:40am and 8:10am PT users may have experienced errors while loading the UI or accessing metric metadata APIs. Data ingest and alerting were not impacted. The issue has since been resolved.

Splunk Synthetic Monitoring will update Google Chrome and Chromium to version 135.0.7049.84-1 for Browser tests on 4/22 at 8 am PST. We periodically auto-update to newer versions of Google Chrome/Chromium when available. Due to differences between browser versions, Synthetics test behavior or timings can sometimes change and may require updates to your configured steps.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

This incident has been resolved.

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

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

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

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

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

This incident has been resolved.

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

We are currently investigating this issue.

This incident has been resolved.

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

We are currently investigating this issue.

Customers may have been experiencing delays in some charts and detectors between 4.22pm PST and 6.01pm PST.

This incident has been resolved.

We are continuing to monitor for any further issues.

We are seeing signs of recovery and are continuing to monitor.

Splunk Synthetics runners are unavailable in the Stockholm region due to an AWS EC2 instance outage in the eu-north-1 region.

This incident has been resolved.

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

We are continuing to work on a fix for this issue.

We are continuing to work on a fix for this issue.

We are continuing to work on a fix for this issue.

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

We are continuing to investigate this issue.

A degradation in the Splunk RUM metrics processing pipeline is causing Monitoring MetricSets to be dropped. Alerts, charts, and detectors built from Monitoring MetricSets are impacted. A degradation in the performance of the Splunk RUM trace processing pipeline is causing Troubleshooting MetricSets to be delayed by more than fifteen minutes. As a result, the RUM Troubleshooting experience does not have access to the most recent data.

This incident has been resolved.

We are continuing to monitor for any further issues. No monitoring metric data is being lost at this time, but the most recent data may not be available.

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

We are continuing to work on a fix for this issue.

We are continuing to work on a fix for this issue.

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

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

A degradation of the ingest path for Splunk RUM is causing monitoring data to be dropped and lost. We are investigating the issue and will provide an update as soon as possible.

This incident has been resolved.

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

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

A degradation in the performance of the Splunk RUM metrics processing pipeline is causing Monitoring MetricSets to be delayed by more than five minutes. Trace data ingest is not impacted, but alerts, charts and detectors built from Monitoring MetricSets are impacted

Data processing of Real User Monitoring lagged behind ingest.

This incident has been resolved.

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

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

We are continuing to investigate this issue.

We are investigating a major outage of the Splunk APM web application. Trace data ingest is not impacted at this time. We will provide an update as soon as possible.

This incident has been resolved.

We are continuing to investigate this issue.

We are investigating a major outage of the Splunk RUM web application. Session data ingest is not impacted at this time. We will provide an update as soon as possible.

This incident has been resolved.

We are investigating a major outage of the Splunk APM web application. Trace data ingest is not impacted at this time. We will provide an update as soon as possible.

We are investigating a major outage of the Splunk APM web application. Trace data ingest is not impacted at this time. We will provide an update as soon as possible.

A degradation of the ingest path for Splunk RUM was causing session data to be dropped and lost. This issue is resolved.

Synthetic Monitoring tests were delayed and now the issue is resolved.

Synthetic Monitoring tests were delayed or skipped and now the issue is resolved.

A degradation of the ingest path for Splunk RUM was causing session data to be dropped and lost. This issue is resolved.

This incident has been resolved.

The system has now recovered, and we are continuing to monitor.

The recovery is ongoing at a steady pace. We will continue to monitor and provide updates

The fixes continue to take effect and we expect the system to recover at a steady pace over the next few hours. We will continue to monitor and provide updates

Additional fixes are now deployed and starting to take effect. We will continue to monitor and provide updates

Additional fixes are now implemented and are in the process of being deployed. We will continue to provide updates.

We are in the process of implementing additional fixes and will continue to provide updates

The fix has been deployed. We are monitoring it and will continue providing updates.

We are continuing to deploy the fix and will provide further updates as it starts taking effect.

The fix has been implemented and is in the process of being deployed.

We are continuing to make progress on a fix for this issue.

We are continuing to make progress on a fix for this issue.

We are continuing to make progress on a fix for this issue.

We are continuing to work on a fix for this issue.

Investigation has confirmed that charts and detectors that rely on property and tag updates on metric time series are impacted. The issue has been identified and a fix is being implemented.

Customers may be experiencing delays in some charts and detectors. Datapoint ingest is not affected. We are investigating and will provide an update shortly.

This incident has been resolved.

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

AWS is currently experiencing an outage. We will continue to monitor until the AWS issue is resolved. The latest information can be found here: https://health.aws.amazon.com/health/status

This incident has been resolved.

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

The UI for a subset of customers may be loading slowly. Datapoint ingest is not affected. We are investigating and will provide an update shortly.

Splunk Synthetic Monitoring updated Google Chrome to version 125 for Browser tests on July 18 at 12:30 PM EDT. 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.

The issue with Cloud Monitoring metrics has been resolved for all affected users as of Monday, 2024-07-15 10:52 US/Pacific.

We are experiencing an issue syncing cloud metrics from GCP. Some metrics from GCP could be delayed or dropped. This is due to a GCP issue. See status page here: https://status.cloud.google.com/incidents/ERzzrJqeGR2GCW51XKFv

Experiencing an issue syncing cloud metrics from GCP. Some metrics from GCP could be delayed.

Customers were unable to access usage and billing reports.

This incident has been resolved.

This incident has been resolved.

The issue has been identified and remediated, and we are still pending confirmation of the full resolution. It did not impact trace data ingest, service-level and endpoint-level Monitoring MetricSets. We are continuing to monitor for further issues.

The issue has been identified and remediated, and we are still pending confirmation of the full resolution. It did not impact trace data ingest, service-level and endpoint-level Monitoring MetricSets. We are continuing to monitor for further issues.

The issue has been identified and remediated, and we are still pending confirmation of the full resolution. It did not impact trace data ingest, service-level and endpoint-level Monitoring MetricSets. We are continuing to monitor for further issues.

The issue has been identified and remediated, and we are still pending confirmation of the full resolution. It did not impact trace data ingest, service-level and endpoint-level Monitoring MetricSets. We are continuing to monitor for further issues.

The issue has been identified and remediated, and we are still pending confirmation of the full resolution. It did not impact trace data ingest, service-level and endpoint-level Monitoring MetricSets. We are continuing to monitor for further issues.

The issue has been identified and remediated, and we are waiting for confirmation of the full resolution. It did not impact trace data ingest, service-level and endpoint-level Monitoring MetricSets. We are continuing to monitor for further issues.

The issue has been identified and remediated. It did not impact trace data ingest, service-level and endpoint-level Monitoring MetricSets. We are continuing to monitor for further issues.

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. This has been occurring since 12:39AM PT. The issue has been identified and remediated, and systems should be recovered within the next hour. We will continue to monitor and provide periodic updates.

This incident has been resolved.

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

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

We are investigating an elevated rate of errors occurring while using the Splunk APM Interface. Parts of the Splunk APM Troubleshooting experience like the service map, map breakdowns, Tag Spotlight and charts within Splunk APM may be impacted and return errors. Trace data ingest is not impacted.

Between 12:02a PT and 12:12a PT a degradation in the performance of the Splunk RUM trace processing pipeline is causing Troubleshooting MetricSets and Monitoring MetricSets to be delayed by more than five minutes. As a result, the RUM Troubleshooting experience does not have access to the most recent data.

Splunk Log Observer web application was unavailable between 10:25 AM to 11:54 AM PDT. Log data ingest was not impacted and this incident is completely resolved.

From 6:48PM ET and 7:08PM, customers may have experienced delays in some charts and detectors. Datapoint ingest was not affected.

A degradation in the performance of the Splunk APM metrics processing pipeline is causing Monitoring MetricSets to be delayed by more than five minutes between 14:44 PDT and 15:05 PDT. Trace data ingest is not impacted, but service, endpoint and workflow dashboards, and other charts and detectors built from Monitoring MetricSets are impacted.

This incident has been resolved.

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

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

We are continuing to monitor for any further issues.

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

We are continuing to work on a fix for this issue.

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

We are currently investigating this issue.

There is a degradation in Observability UI and API performance. Datapoint ingest is not affected. This incident is resolved now. We are monitoring.

This incident has been resolved.

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

We are investigating a major outage of the Splunk Log Observer web application. Log data ingest is not impacted at this time. We will provide an update as soon as possible.

We are experiencing a degradation in the availability of trace exemplars. When clicking on charts to search for trace exemplars, results may not be available. It may not be possible to view individual traces.

The Splunk Observability Cloud web application was unavailable between 1:14pm PST and 1:37pm PST. Data ingest and alerting was not impacted.

This incident has been resolved.

We are investigating a major outage of the Splunk Log Observer web application. Log data ingest is not impacted at this time. We will provide an update as soon as possible.

This incident has been resolved.

We have identified a bug that is causing alerts to be sent for detector rules that have been previously disabled via the API. This issue does not impact detectors that have rules disabled via the UI. Starting January 18, some detectors that had rules disabled via the API (such as through Terraform) continued to send alerts. We are currently rolling out a fix to production systems and expect to resolve the issue within the next 3 hours.

This incident has been resolved.

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.

This incident has been resolved.

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

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 of 7am PT. 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.

This incident has been resolved.

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

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

A degradation in the performance of the Splunk APM trace processing pipeline is causing Monitoring and Troubleshooting MetricSets to be delayed by more than 15 minutes. As a result, the APM Troubleshooting experience, service maps and Tag Spotlight do not have access to the most recent data. In addition, service-level and endpoint-level Monitoring MetricSets and the detectors built from them are also impacted. 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.

Datapoint ingest was affected and dropped a small percentage of datapoints between 11:42am PST and 11:50am PST. This incident has been resolved.

This incident has been resolved.

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

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

Datapoint ingest is affected and we are dropping datapoints. This started at around 2:30pm PST. We are investigating and will provide an update every 15 mins.

This incident has been resolved.

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

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

A degradation in the performance of the Splunk APM trace processing pipeline is causing Troubleshooting MetricSets, Trace storage, and Trace metrics 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.

This incident has been resolved.

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

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

We’re investigating an issue with the Alert Modal chart not displaying plots. Only charts within Alert Modals are impacted. Alerting, notification, and general charting are not impacted.

APM ingest was experiencing increased latencies between 8:33-8:39 am PST. The system is recovered and we are continuing to monitor the system.

APM ingest was experiencing increased latencies between 11:05-11:20 am PST. The system is recovered and we are continuing to monitor the system.

A degradation in the performance of the Splunk APM metrics processing pipeline caused Trace Monitoring MetricSets to be delayed by more than five minutes between 12.53am PST and 1.21am PST. Trace data ingest was not impacted, but service, endpoint and workflow dashboards, and other charts and detectors built from Trace Monitoring MetricSets were impacted.

This incident has been resolved.

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

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

We are investigating an issue with the Splunk APM web application. Trace data ingest is not impacted at this time. The service map may not properly load or may display an error.

This incident has been resolved.

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

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

We are continuing to investigate this issue.

A degradation of the trace data ingest path for Splunk APM is causing trace spans to be dropped and lost. We are investigating the issue and will provide an update as soon as possible.

Customers may have experienced delays in seeing newly created MetricTimeSeries between 8:48AM and 8:58AM PDT. Datapoint ingest was not affected. The issue has been resolved.

This incident has been resolved.

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

We are investigating a major outage of the Splunk RUM web application. Session data ingest is not impacted at this time. We will provide an update as soon as possible.