Splunk outage on May 28, 2026
Splunk users likely saw failed connections, degraded availability, or session instability for this Monitoring service. The incident reached Major severity and lasted 3h. The stored report window does not show a preserved user-report spike.
May 28, 00:15 UTC Identified - 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
Deterministic readout · awaiting AI summary pass
Incident detected
Major confidence crossed the incident threshold for Splunk: aWS Privatelink unable to receive HEC data with multiple AWS regions impacted | #cinc-66607_cloud_multiple_privatelink (Major Outage).
Marked resolved
The incident was closed after 3h of observed impact.
No per-source signal payloads were preserved in this incident's snapshot window.
Confidence scoring
80.00The incident reached 80.00 peak confidence across available stored status snapshots.
User reports
0 / 15mNo elevated user-report volume was preserved in the incident window snapshots.
Status samples
0 affectedThe incident row exists, but the bounded snapshot window does not include affected status samples.
Recovery signal
ResolvedRecovery was recorded at Thu, May 28, 2026, 03:15 AM UTC.