Is Splunk down in the US?
Vendor reports no incidentWhat Splunk reports
Splunk reports no incident on its status page.
As of the last successful poll, 2026-11-05 15:01 UTC.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingin the US, measured from Ashburn and San Jose
All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Splunk at Nov 5, 2026, 3:04 PM UTC.
Over the last 24 hours we completed 254 checks from Ashburn and San Jose and 254 answered cleanly, 100.00% availability.
Of the 2 other regions we check Splunk from, all 2 read checks passing right now.
Email me when Splunk reports an incident on its status page, and again when it reports it resolved.
What our Ashburn and San Jose probes measured
Last checked Nov 5, 2026, 3:04 PM UTC.
Splunk from Ashburn and San Jose over the last 30 days
Over the last 30 days, Splunk answered our Ashburn probe in 996 ms on average, and 1 check in 20 took longer than 1,492 ms.
Over the last 30 days, Splunk answered our San Jose probe in 1,332 ms on average, and 1 check in 20 took longer than 1,995 ms.
Ranked by average response time across the 4 cities we check Splunk from, Ashburn 2nd, San Jose 3rd; Frankfurt was fastest at 802 ms and Tokyo slowest at 1,764 ms.
From Ashburn and San Jose we ran 759 checks of Splunk in 4 days, and 759 answered cleanly: 100.00% availability.
Every one of those days was clean: not one failed check.
In Ashburn local time (EST), Splunk was slowest around 9 PM, at 1,159 ms on average over the last 14 days, and quickest around 1 PM, at 852 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Thu, Nov 5 | 158 | 100.00% | 1,116 ms |
| Wed, Nov 4 | 251 | 100.00% | 1,107 ms |
| Tue, Nov 3 | 246 | 100.00% | 1,204 ms |
| Mon, Nov 2 | 104 | 100.00% | 1,118 ms |
Splunk outages measured from the US
Our Ashburn and San Jose probes measured no confirmed Splunk outage in the last 90 days.
How the other regions read right now
Of the 2 other regions we check Splunk from, all 2 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Frankfurt | Checks passing | 100.00% of 99 checks |
| Tokyo | Checks passing | 100.00% of 60 checks |
Other countries we check Splunk from
How we measured this
The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Splunk's public endpoints. They are not user reports, and they are not Splunk's own status page.
See Splunk's full check readings, the 90-day history by region, or the outage tracker methodology.
The US readings here are taken from that country and show the time of the last one, but Splunk has not yet accumulated enough continuous history for us to publish this page to search engines.
Check your own site from Ashburn
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter