Splunk Observability Cloud US2 incident

[US2] Azure Monitor and GCP Cloud Monitoring metrics not fetched

Major Resolved View vendor source →

Splunk Observability Cloud US2 experienced a major incident on May 12, 2026 affecting Splunk Cloud Metric Syncer, lasting 11h. The incident has been resolved; the full update timeline is below.

Started
May 12, 2026, 10:30 PM UTC
Resolved
May 13, 2026, 09:30 AM UTC
Duration
11h
Detected by Pingoru
May 12, 2026, 10:30 PM UTC

Affected components

Splunk Cloud Metric Syncer

Update timeline

  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.