Splunk Observability Cloud US2 incident

Synthetics tests running from Bahrain may not run on schedule

Minor Resolved View vendor source →

Splunk Observability Cloud US2 experienced a minor incident on March 25, 2026, lasting 27d 22h. The incident has been resolved; the full update timeline is below.

Started
Mar 25, 2026, 05:41 AM UTC
Resolved
Apr 22, 2026, 04:32 AM UTC
Duration
27d 22h
Detected by Pingoru
Mar 25, 2026, 05:41 AM UTC

Update timeline

  1. monitoring Mar 25, 2026, 05:41 AM UTC

    Mar 24, 11:20 PDT Update - The issue has been identified as a regional cloud provider outage that is impacting our ability to maintain Synthetics testing in specific areas. Due to the uncertainty regarding the resolution timeline for this issue, we have made the decision to temporarily remove the following locations from our Synthetics testing network: Bahrain Muscat UAE We recommend reviewing your current test configurations and selecting alternative testing locations if necessary to ensure continued coverage. Our engineering team is monitoring the situation closely. We will provide further updates as more information becomes available from the cloud provider. We apologize for any inconvenience this may cause and appreciate your patience as we work to maintain the reliability of our services. Mar 23, 17:57 PDT Update - The issue has been identified as an outage affecting the Bahrain region due to a Cloud Provider outage. We recommend that users temporarily run their Synthetic Monitoring tests from an alternative location while this issue is being resolved by the Cloud Provider. Mar 23, 16:29 PDT Identified - The issue has been identified and is due to a Cloud Provider outage in the Bahrain region.