Splunk Observability Cloud AU0 Outage History

Splunk Observability Cloud AU0 is up right now

Splunk Observability Cloud AU0 had 38 outages in the last 2 years totaling 26h 39m of downtime — averaging 1.6 incidents per month.

There were 38 Splunk Observability Cloud AU0 outages since June 4, 2024 totaling 26h 39m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.au0.signalfx.com

Notice August 21, 2025

Elevated Error Rate from the Splunk APM API

Detected by Pingoru
Aug 21, 2025, 02:30 AM UTC
Resolved
Aug 21, 2025, 02:45 AM UTC
Duration
14m
Affected: Splunk APM API
Timeline · 4 updates
  1. investigating Aug 21, 2025, 01:26 AM UTC

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

  2. identified Aug 21, 2025, 04:36 AM UTC

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

  3. monitoring Aug 21, 2025, 04:36 AM UTC

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

  4. resolved Aug 21, 2025, 04:37 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical July 11, 2025

Corrupted Session Replay data

Detected by Pingoru
Jul 11, 2025, 07:10 PM UTC
Resolved
Jul 11, 2025, 08:50 PM UTC
Duration
1h 39m
Affected: Session Replay APISession Replay Processor
Timeline · 3 updates
  1. identified Jul 11, 2025, 07:10 PM UTC

    An issue in the session replay processing pipeline is causing session replay data to be corrupted. Session replay data ingest is not impacted. We have identified the issue and are working on fixing it.

  2. monitoring Jul 11, 2025, 08:45 PM UTC

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

  3. resolved Jul 11, 2025, 10:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 20, 2025

Splunk APM MetricSets Delayed

Detected by Pingoru
Jun 20, 2025, 11:18 PM UTC
Resolved
Jun 20, 2025, 11:12 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 20, 2025, 11:18 PM UTC

    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 during 12:10 - 12:40PM PDT on June 20th. A portion of Troubleshooting MetricSets were delayed. Monitoring MetricSets were delayed for metrics derived from Traces and Business Workflows, but not for metrics derived from Services and Spans. It may impact detectors on Traces and Business Workflows.

Read the full incident report →

Major April 17, 2025

Log Observer Connect Search Failures

Detected by Pingoru
Apr 17, 2025, 11:30 AM UTC
Resolved
Apr 17, 2025, 06:34 PM UTC
Duration
7h 3m
Affected: Log Observer Connect Search
Timeline · 4 updates
  1. investigating Apr 17, 2025, 06:08 PM UTC

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

  2. identified Apr 17, 2025, 06:11 PM UTC

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

  3. monitoring Apr 17, 2025, 06:21 PM UTC

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

  4. resolved Apr 17, 2025, 06:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 14, 2025

Unable to fetch Splunk RUM sessions

Detected by Pingoru
Apr 14, 2025, 08:40 PM UTC
Resolved
Apr 15, 2025, 04:39 AM UTC
Duration
7h 59m
Affected: Splunk RUM API
Timeline · 4 updates
  1. investigating Apr 15, 2025, 04:35 AM UTC

    We are currently investigating this issue.

  2. investigating Apr 15, 2025, 04:36 AM UTC

    We are continuing to investigate this issue.

  3. investigating Apr 15, 2025, 04:37 AM UTC

    We are continuing to investigate this issue.

  4. resolved Apr 15, 2025, 04:39 AM UTC

    The issue has been resolved.

Read the full incident report →

Major February 21, 2025

Charts Not Loading

Detected by Pingoru
Feb 21, 2025, 01:21 AM UTC
Resolved
Feb 21, 2025, 02:08 AM UTC
Duration
47m
Affected: Splunk Observability Cloud Web Interface
Timeline · 6 updates
  1. investigating Feb 21, 2025, 01:21 AM UTC

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

  2. investigating Feb 21, 2025, 01:21 AM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 21, 2025, 01:30 AM UTC

    We are continuing to investigate this issue.

  4. investigating Feb 21, 2025, 01:31 AM UTC

    Charts for some customers may not be loading. Datapoint ingest is not affected. We are investigating and will provide an update shortly.

  5. monitoring Feb 21, 2025, 01:42 AM UTC

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

  6. resolved Feb 21, 2025, 02:08 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 14, 2025

Splunk Synthetics runners are unavailable in the Stockholm region

Detected by Pingoru
Feb 14, 2025, 12:17 AM UTC
Resolved
Feb 14, 2025, 04:21 AM UTC
Duration
4h 3m
Affected: Splunk Synthetics Monitoring Runners
Timeline · 4 updates
  1. investigating Feb 14, 2025, 12:17 AM UTC

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

  2. monitoring Feb 14, 2025, 12:43 AM UTC

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

  3. monitoring Feb 14, 2025, 02:29 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Feb 14, 2025, 04:21 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 28, 2025

Splunk APM Trace Data Ingestion Delayed

Detected by Pingoru
Jan 28, 2025, 06:04 PM UTC
Resolved
Jan 28, 2025, 06:29 PM UTC
Duration
25m
Affected: Splunk APM Trace Data
Timeline · 3 updates
  1. investigating Jan 28, 2025, 06:09 PM 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. monitoring Jan 28, 2025, 06:14 PM UTC

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

  3. resolved Jan 28, 2025, 06:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 3, 2025

Splunk RUM Sessions Delayed

Detected by Pingoru
Jan 03, 2025, 03:16 AM UTC
Resolved
Jan 03, 2025, 12:46 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jan 03, 2025, 03:16 AM UTC

    A degradation in the performance of the Splunk RUM trace data ingestion pipeline caused the processing and storage of sessions to be delayed by more than five minutes. No data was being lost. The issue resolved at 5:38 PM PT.

Read the full incident report →

Minor September 13, 2024

Splunk Observability Cloud API and Web Interface is slow

Detected by Pingoru
Sep 13, 2024, 02:15 PM UTC
Resolved
Sep 13, 2024, 03:25 PM UTC
Duration
1h 9m
Affected: Splunk Observability Cloud Web InterfaceSplunk Observability Cloud API
Timeline · 3 updates
  1. investigating Sep 13, 2024, 03:02 PM UTC

    Splunk Observability Cloud API and Web Interface have degraded performance. We are currently investigating the root cause.

  2. monitoring Sep 13, 2024, 03:17 PM UTC

    Performance is back to normal. We are monitoring the issue.

  3. resolved Sep 13, 2024, 03:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 18, 2024

Splunk Synthetic Monitoring updated Google Chrome to version 125

Detected by Pingoru
Jul 18, 2024, 04:30 PM UTC
Resolved
Jul 18, 2024, 04:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jul 22, 2024, 08:26 PM UTC

    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.

Read the full incident report →

Major July 15, 2024

Delayed metrics from GCP

Detected by Pingoru
Jul 15, 2024, 05:02 PM UTC
Resolved
Jul 15, 2024, 06:54 PM UTC
Duration
1h 51m
Affected: Cloud Integrations
Timeline · 4 updates
  1. investigating Jul 15, 2024, 05:02 PM UTC

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

  2. investigating Jul 15, 2024, 05:40 PM UTC

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

  3. identified Jul 15, 2024, 05:52 PM UTC

    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

  4. resolved Jul 15, 2024, 06:54 PM UTC

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

Read the full incident report →

Major June 4, 2024

Splunk Observability Cloud Web Interface Unavailable

Detected by Pingoru
Jun 04, 2024, 07:04 AM UTC
Resolved
Jun 04, 2024, 08:28 AM UTC
Duration
1h 23m
Affected: Splunk Observability Cloud Web InterfaceSplunk Observability Cloud API
Timeline · 8 updates
  1. investigating Jun 04, 2024, 07:22 AM UTC

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

  2. investigating Jun 04, 2024, 07:25 AM UTC

    We are continuing to investigate this issue.

  3. investigating Jun 04, 2024, 07:42 AM UTC

    We are continuing to investigate this issue.

  4. investigating Jun 04, 2024, 07:54 AM UTC

    We are continuing to investigate this issue.

  5. investigating Jun 04, 2024, 08:09 AM UTC

    We are continuing to investigate this issue.

  6. monitoring Jun 04, 2024, 08:15 AM UTC

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

  7. monitoring Jun 04, 2024, 08:25 AM UTC

    We are continuing to monitor for any further issues.

  8. resolved Jun 04, 2024, 08:28 AM UTC

    This incident has been resolved.

Read the full incident report →