Splunk Observability Cloud JP0 incident

Corrupted Session Replay data

Critical Resolved View vendor source →

Splunk Observability Cloud JP0 experienced a critical incident on July 11, 2025 affecting Session Replay Processor and Session Replay API, lasting 1h 35m. The incident has been resolved; the full update timeline is below.

Started
Jul 11, 2025, 07:15 PM UTC
Resolved
Jul 11, 2025, 08:50 PM UTC
Duration
1h 35m
Detected by Pingoru
Jul 11, 2025, 07:15 PM UTC

Affected components

Session Replay ProcessorSession Replay API

Update timeline

  1. identified Jul 11, 2025, 07:15 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:35 PM UTC

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

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

    This incident has been resolved.