Is Splunk Down?
Reachable from all 8 checked regions
Average response time: 551ms
Last checked · checks run every 6 hours
Official status page: https://status.splunkcloud.com
Splunk uptime
Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 71 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
30-day history
71-day clean streakReachability by region
Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.
What Splunk does
Splunk collects machine data such as logs, metrics and events, indexes it, and makes it searchable for operations and security teams. It is the system people open during someone else's outage, which is why its own availability matters more than its traffic volume suggests. Splunk Cloud Platform is the hosted version; many organisations also run Splunk Enterprise on their own infrastructure.
What an outage looks like
Searches hang, return partial result sets, or fail outright. Dashboards and scheduled reports render empty panels. New data stops appearing, so recent events are missing from search even after indexing recovers and older data still queries fine. Alerts built on saved searches may not fire at all, which is the failure mode security teams notice last.
What to do about it
Check status.splunkcloud.com, which covers Splunk Cloud Platform and lists Login, Search, Index and Infrastructure as separate components, along with Detection Studio, Threat Intel Management, Ingest Processor and Edge Processor. Search failing while Index is healthy means a different problem from ingestion stopping. If you run Splunk Enterprise on your own infrastructure, that status page does not describe your deployment and the fault is likely local.
Is it down for everyone, or just you?
If this page says Splunk is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Splunk outage FAQ
Does status.splunkcloud.com cover self-hosted Splunk Enterprise?
Is data lost during a Splunk ingestion outage?
Will my alerts fire once Splunk recovers?
Is Splunk down, or is my search just slow?
How we measure this
- We request Splunk's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Splunk publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.
Get alerted when Splunk goes down
This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring