Splunk incident

Search and Ingest | (Major Outage)

Critical Resolved View vendor source →

Splunk experienced a critical incident on August 19, 2025 affecting Ingest and Search, lasting 6h 5m. The incident has been resolved; the full update timeline is below.

Started
Aug 19, 2025, 04:56 PM UTC
Resolved
Aug 19, 2025, 11:01 PM UTC
Duration
6h 5m
Detected by Pingoru
Aug 19, 2025, 04:56 PM UTC

Affected components

IngestSearch

Update timeline

  1. investigating Aug 19, 2025, 04:56 PM UTC

    We are investigating a potential issue with search and ingest that may impact customers on Splunk Cloud Platform for FedRAMP High and Splunk Cloud Platform for IL5. As a result of the issue, customer search and indexing may experience issues completing successfully. We will provide an update within the next 30 minutes.

  2. identified Aug 19, 2025, 05:25 PM UTC

    We have identified the source of the issue and are currently working on implementing a fix.

  3. identified Aug 19, 2025, 05:57 PM UTC

    We continue working to implement a fix for this issue.

  4. identified Aug 19, 2025, 06:26 PM UTC

    We are starting to see recovery on some of the impacted instances. Teams continue to work on implementing a fix for this issue.

  5. identified Aug 19, 2025, 06:54 PM UTC

    We see recovery on some of the impacted instances. Teams continue to work on implementing a fix for this issue.

  6. identified Aug 19, 2025, 07:23 PM UTC

    We continue working to implement a fix for this issue.

  7. identified Aug 19, 2025, 07:53 PM UTC

    We continue working to implement a fix for this issue.

  8. identified Aug 19, 2025, 08:22 PM UTC

    We continue working to implement a fix for this issue.

  9. identified Aug 19, 2025, 08:50 PM UTC

    We continue working to implement a fix for this issue.

  10. identified Aug 19, 2025, 09:19 PM UTC

    We continue working to implement a fix for this issue.

  11. identified Aug 19, 2025, 09:49 PM UTC

    We continue working to implement a fix for this issue.

  12. monitoring Aug 19, 2025, 09:56 PM UTC

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

  13. monitoring Aug 19, 2025, 10:27 PM UTC

    We are continuing to monitor for any further issues.

  14. monitoring Aug 19, 2025, 11:00 PM UTC

    We are continuing to monitor for any further issues.

  15. resolved Aug 19, 2025, 11:01 PM UTC

    This incident has been resolved.