Splunk Observability Cloud JP0 incident

Splunk Observability Synthetic Monitoring Results Processing delayed

Minor Resolved View vendor source →

Splunk Observability Cloud JP0 experienced a minor incident on June 2, 2026 affecting Splunk Synthetics Monitoring Results processing, lasting 6h 58m. The incident has been resolved; the full update timeline is below.

Started
Jun 02, 2026, 09:45 AM UTC
Resolved
Jun 02, 2026, 04:44 PM UTC
Duration
6h 58m
Detected by Pingoru
Jun 02, 2026, 09:45 AM UTC

Affected components

Splunk Synthetics Monitoring Results processing

Update timeline

  1. investigating Jun 02, 2026, 09:45 AM UTC

    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.

  2. investigating Jun 02, 2026, 10:45 AM UTC

    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.

  3. investigating Jun 02, 2026, 11:45 AM UTC

    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.

  4. investigating Jun 02, 2026, 12:57 PM UTC

    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.

  5. resolved Jun 02, 2026, 04:44 PM UTC

    We have identified and remediated an issue affecting synthetic test result ingestion for a subset of customers. We apologize for any inconvenience this may have caused and thank you for your patience. Time range of impact: June 1 17:30 UTC - June 2 14:30 UTC