Splunk incident
Cloud Region Network Connectivity Impact | CINC-66292 (Major Outage)
Splunk experienced a minor incident on May 8, 2026 affecting Ingest and Search and 1 more component, lasting 2d 13h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 08, 2026, 01:53 AM UTC
We are investigating an issue indicating an AWS outage in us-east-1. As a result, the Splunk Cloud Platform environment may be inaccessible for limited number of customers in the specified region. Our teams are working with the provider to resolve this issue. Your patience is greatly appreciated and we will provide more updates upon resolution.
- investigating May 08, 2026, 03:01 AM UTC
We are investigating an issue indicating one of our suppliers experiencing outage in us-east-1. As a result, the Splunk Cloud Platform environment may be inaccessible for limited number of customers in the specified region. Our teams are working with the provider to resolve this issue. Your patience is greatly appreciated and we will provide more updates upon resolution.
- investigating May 08, 2026, 03:28 AM UTC
We continue to investigate an issue indicating one of our suppliers experiencing in us-east-1. As a result, the Splunk Cloud Platform environment may be inaccessible for limited number of customers in the specified region. Our teams are working with the provider to resolve this issue. Your patience is greatly appreciated and we will provide more updates upon resolution.
- investigating May 08, 2026, 04:26 AM UTC
As teams continue to investigate we will tentatively provide our next update by 05:00 AM UTC, or sooner if new information becomes available.
- investigating May 08, 2026, 05:35 AM UTC
Investigation is in progress, we will provide our next update by 07:00 AM UTC, or sooner if new information becomes available.
- investigating May 08, 2026, 06:49 AM UTC
Investigation is in progress, we will provide our next update by 09:00 AM UTC, or sooner if new information becomes available.
- investigating May 08, 2026, 09:03 AM UTC
Investigation is ongoing, and remediation efforts are in progress. We will provide our next update by 10:00 UTC, or sooner if new information becomes available.
- investigating May 08, 2026, 09:59 AM UTC
Investigation is ongoing, and remediation efforts are in progress. We will provide our next update by 11:00 UTC, or sooner if new information becomes available.
- investigating May 08, 2026, 11:30 AM UTC
Investigation remains ongoing, and we continue to make progress toward recovery. Some affected infrastructure has stabilized, but some customers may still experience impact while remediation continues. Based on current recovery efforts, full restoration is expected to take several more hours. We will provide our next update by 13:00 UTC, or sooner if new information becomes available.
- investigating May 08, 2026, 01:29 PM UTC
Update still investigating and recovery efforts remain in progress. Some impacted environments have shown improvement, but some customers may continue to experience service impact while remediation and validation continue. We will provide our next update by 15:00 UTC, or sooner if new information becomes available.
- investigating May 08, 2026, 02:21 PM UTC
Update still investigating and recovery efforts remain in progress. Some impacted environments have shown improvement, but some customers may continue to experience service impact while remediation and validation continue. We will provide our next update by 17:00 UTC, or sooner if new information becomes available.
- investigating May 08, 2026, 04:42 PM UTC
Update still investigating and recovery efforts remain in progress. Some impacted environments have shown improvement, but some customers may continue to experience service impact while remediation and validation continue. We will provide our next update by 19:00 UTC, or sooner if new information becomes available.
- investigating May 08, 2026, 07:01 PM UTC
We are still investigating and recovery efforts remain in progress. Some impacted environments have shown improvement, but some customers may continue to experience service impact while remediation and validation continue. We will provide our next update by 21:00 UTC, or sooner if new information becomes available.
- investigating May 08, 2026, 09:15 PM UTC
We are still investigating and recovery efforts remain in progress. Some impacted environments have shown improvement, but some customers may continue to experience service impact while remediation and validation continue. We will provide our next update by 23:00 UTC, or sooner if new information becomes available.
- investigating May 08, 2026, 11:15 PM UTC
Service restoration is progressing steadily following the implementation of our mitigation efforts. While most environments have recovered, some customers may still experience intermittent impact as we finalize remediation and validation. Our team is actively monitoring all systems to ensure full stability.
- identified May 09, 2026, 06:57 AM UTC
Service restoration is progressing steadily following the implementation of our mitigation efforts. While most environments have recovered, some customers may still experience intermittent impact as we finalize remediation and validation. Our team is actively monitoring all systems to ensure full stability.
- identified May 09, 2026, 02:46 PM UTC
Recovery continues following mitigation efforts. Most environments have recovered, though some customers may still experience intermittent impact while final remediation and validation are completed. Our team is actively monitoring to confirm full stability.
- identified May 10, 2026, 01:04 AM UTC
Recovery continues to progress following our mitigation efforts. Most environments are operating normally, and we’re seeing stable performance across the majority of systems. A small number of customers may still experience intermittent impact as we complete final remediation and validation. Our team remains actively engaged and monitoring closely to confirm full stability.
- resolved May 10, 2026, 03:29 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-66292.