Splunk incident

Victoria Experience | CINC-57465 (Degraded Performance)

Notice Resolved View vendor source →

Splunk experienced a notice incident on July 31, 2024 affecting Ingest and Search and 1 more component, lasting 19h 4m. The incident has been resolved; the full update timeline is below.

Started
Jul 31, 2024, 12:01 AM UTC
Resolved
Jul 31, 2024, 07:06 PM UTC
Duration
19h 4m
Detected by Pingoru
Jul 31, 2024, 12:01 AM UTC

Affected components

IngestSearchIndex

Update timeline

  1. investigating Jul 31, 2024, 12:01 AM UTC

    We are seeing an issue impacting the Indexer tier for customers on Victoria Experience. As a result of the issue, your indexers may experience a restart every 72 hours. We will provide an update as soon as possible.

  2. identified Jul 31, 2024, 12:37 AM UTC

    We have identified the source of the issue for Victoria Experience customers and are currently working on implementing a fix. Your patience is greatly appreciated and we will provide more updates as we implement the fix.

  3. identified Jul 31, 2024, 03:20 AM UTC

    We have identified the source of the issue for Victoria Experience customers and are currently working on implementing a fix. Your patience is greatly appreciated and we will provide more updates as we implement the fix.

  4. identified Jul 31, 2024, 05:53 AM UTC

    We have identified the source of the issue for Victoria Experience customers and are currently working on implementing a fix. Your patience is greatly appreciated and we will provide more updates as we implement the fix.

  5. identified Jul 31, 2024, 07:15 AM UTC

    We have identified the source of the issue for Victoria Experience customers and are currently implementing a fix. Your patience is greatly appreciated and we will provide more updates as we continue to implement the fix.

  6. identified Jul 31, 2024, 08:15 AM UTC

    We have identified the source of the issue for Victoria Experience customers and are currently implementing a fix. Your patience is greatly appreciated and we will provide more updates as we continue to implement the fix.

  7. identified Jul 31, 2024, 09:16 AM UTC

    We have identified the source of the issue for Victoria Experience customers and are currently implementing a fix. Your patience is greatly appreciated and we will provide more updates as we continue to implement the fix.

  8. identified Jul 31, 2024, 10:15 AM UTC

    We have identified the source of the issue for Victoria Experience customers and are currently implementing a fix. Your patience is greatly appreciated and we will provide more updates as we continue to implement the fix.

  9. identified Jul 31, 2024, 11:15 AM UTC

    We have identified the source of the issue for Victoria Experience customers and are currently implementing a fix. Your patience is greatly appreciated and we will provide more updates as we continue to implement the fix.

  10. identified Jul 31, 2024, 12:17 PM UTC

    We have identified the source of the issue for Victoria Experience customers and are currently implementing a fix. Your patience is greatly appreciated and we will provide more updates as we continue to implement the fix.

  11. identified Jul 31, 2024, 01:15 PM UTC

    We have identified the source of the issue for Victoria Experience customers and are currently implementing a fix. Your patience is greatly appreciated and we will provide more updates as we continue to implement the fix.

  12. identified Jul 31, 2024, 02:15 PM UTC

    We have identified the source of the issue for Victoria Experience customers and are currently implementing a fix. Your patience is greatly appreciated and we will provide more updates as we continue to implement the fix.

  13. monitoring Jul 31, 2024, 05:07 PM UTC

    We have implemented a fix for this issue. During this time we are monitoring the results to confirm the resolution and will continue to provide any additional updates once available.

  14. resolved Jul 31, 2024, 07:06 PM UTC

    This issue has been resolved. Teams will now begin their root cause analysis. If you believe that you are still impacted by this issue please contact customer support and reference CINC-57465.