Splunk incident
AWS Privatelink unable to receive HEC data with multiple AWS regions impacted | #cinc-66607_cloud_multiple_privatelink (Major Outage)
Splunk experienced a minor incident on May 28, 2026 affecting Ingest, lasting 1h 28m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 28, 2026, 12:15 AM UTC
We’re investigating an issue affecting some customers hosted in ap-northeast-1, eu-central-1, and us-east-1. Impacted Splunk Cloud Platform customers in these regions may experience access issues. Our teams are actively working to restore service, and we’ll share updates as more information becomes available
- monitoring May 28, 2026, 01:27 AM UTC
A mitigation has been successfully applied across the fleet. Engineering teams are actively monitoring to confirm service has been fully restored and to ensure no further interruptions occur.
- identified May 28, 2026, 01:31 AM UTC
We identified an issue caused by an internal change on May 26, 2026, that impacted ingestion through a PrivateLink. A fix has been identified, released and is currently rolling out. Some customers may continue to experience impact while the fix is being applied. We’ll provide another update once rollout is complete. Our teams are actively working to restore service and will provide another update as soon as more information is available
- monitoring May 28, 2026, 01:41 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 28, 2026, 01:43 AM UTC
The incident has been resolved. Our investigation determined that an internal configuration change began impacting service at 20:34 UTC on May 27, 2026. A fix was developed and rolled out beginning at 23:45 UTC, with full remediation completed by 03:45 UTC on May 28, 2026. We apologise for any inconvenience this caused and appreciate your patience while our teams worked to restore service.