Splunk Cloud Outage History

Splunk Cloud experienced a major outage lasting 61.6 hours due to a network connectivity issue with a third-party supplier in the us-east-1 region, making the platform inaccessible for a limited number of customers. The incident affected core components including Ingest, Search, and Index functionality. Recovery was gradual with most environments restored progressively, and the issue was fully resolved after teams worked with the supplier to implement mitigation efforts.

Splunk Cloud experienced a major search outage lasting 2.4 hours, beginning at 16:34 UTC, that caused degraded search performance and intermittent UI errors. Engineering teams identified the root cause and implemented a fix, with service recovery observed for the majority of customers before full resolution. The incident was fully resolved at 20:41 UTC after continued monitoring to ensure all services returned to normal operation.

Splunk Cloud experienced a major internal IT service disruption that affected core functionality including login, data ingestion, search capabilities, and indexing for 6.3 hours. All planned maintenance activities were paused or canceled during the incident. The service was stabilized after monitoring and fully resolved.

A KVservice issue in Splunk Cloud impacted Enterprise Security search performance for 1.3 hours, affecting ad-hoc, saved, and scheduled searches, particularly those using lookup commands for KV collections. Users experienced inability to save searches within the ES application, errors updating application settings like credentials, and failures in Mission Control and Analyst Queue dashboards. The engineering team identified the root cause and successfully implemented a fix, restoring full operational status to all searches and dashboards.

A cloud service provider outage in the Middle East region affected Splunk Cloud customers' ability to login, search data, and ingest new data for over 3 weeks. Cisco engineers resolved the issue by transitioning affected services out of the impacted region. All affected customers were contacted individually with specific remediation steps through proactive support cases.