Splunk Cloud Outage History
16 incidents recorded over the last 365 days, 15 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Splunk Cloud Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 31, 2026 | Splunkbase is DownSplunk has resolved the issue affecting Splunkbase at splunkbase.splunk.com. Users should now be able to access Splunkbase, download apps, and install apps in Splunk Cloud through the UI as expected. We apologize for… | 47 min | Resolved |
| May 29, 2026 | Expected Restart(s) Following Maintenance ActivityThis incident has been resolved. | 53h 28m | Resolved |
| May 29, 2026 | Admin Config Service (ACS) Maintenance WindowThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| May 28, 2026 | DNS synchronization issue affecting HEC dash DNS records | #cinc-66607_cloud_multiple(Degraded Performance)Some customers experienced traditional HEC ingestion issues due to a DNS synchronization issue affecting HEC dash DNS records using the format http-inputs-${stack}.splunkcloud.com. HEC ingestion using the current… | 59 min | Resolved |
| May 28, 2026 | AWS Privatelink unable to receive HEC data with multiple AWS regions impacted | #cinc-66607_cloud_multiple_privatelink (Major Outage)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… | 1h 28m | Resolved |
| May 8, 2026 | Cloud Region Network Connectivity Impact | CINC-66292 (Major Outage)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 <a… | 61h 35m | Resolved |
| May 4, 2026 | Search outage | CINC-66213 (Major Outage)This incident has been resolved. | 2h 22m | Resolved |
| May 2, 2026 | Internal IT issue (Major Outage)This incident has been resolved. | 6h 17m | Resolved |
| Apr 9, 2026 | Service Advisory: KVservice issues impacting Enterprise Security search performanceOur engineering team has successfully implemented the fix for the KVservice issue. We have monitored the environment and can confirm that there are no recurring errors. All searches and dashboards within the Enterprise… | 1h 15m | Resolved |
| Mar 3, 2026 | Cloud Provider Outage Affecting UAE RegionCisco has confirmed that the impact of the cloud service provider outage in the Middle East has been mitigated. Cisco engineers have successfully transitioned affected services out of the region. We have identified all… | 527h 20m | Resolved |
| Nov 18, 2025 | Multiple Services OutageAll impacted services have been fully remediated. Systems are operating normally, and no further impact is expected. We will continue to monitor to ensure full service stability. Thank you for your patience throughout… | 9h 0m | Resolved |
| Nov 13, 2025 | ACS (Admin Config Service) Down | CINC-63336All ACS services are now operating normally, and our monitoring indicates requests are being processed successfully. We will implement a permanent fix during a scheduled maintenance window, and no customer impact is… | 9h 0m | Resolved |
| Nov 4, 2025 | Login unavailable | CINC-63161 | Major OutageThis issue has been resolved. Teams will now begin their root cause analysis. If you believe that you are still impacted by this issue please <a… | 2h 39m | Resolved |
| Oct 24, 2025 | Lookups failing for KVService | CINC - 62975 | Major OutageThis incident has been resolved after applying the fix. | 15h 18m | Resolved |
| Oct 20, 2025 | Cloud Region Network Connectivity Impact | CINC-62871 (Major Outage)AWS has reported that the earlier issues impacting services in the US-EAST-1 (N. Virginia) region have been fully resolved as of 3:01 PM PDT. All impacted services have returned to normal operations. Users may continue… | 12h 58m | Resolved |
| Sep 22, 2025 | Splunk Mobile app cannot connect to Splunk Secure GatewayA software fix has been provided for release to consumers. iOS version 2.44.0 is ready and available for customer download via the App Store. Android version 2.43.1 is awaiting review and will be released in the… | 8h 53m | Resolved |
How to Read This Splunk Cloud Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Splunk Cloud acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Splunk Cloud outage in this window ran 21d 23h, against a mean recovery of 1d 20h. If you depend on Splunk Cloud in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.