Skip to content

Outage tracker / Splunk / In Japan

Is Splunk down in Japan?

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.

Splunk's status page

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 Japan, measured from Tokyo

Our Tokyo probe last checked Splunk at Nov 5, 2026, 3:03 PM UTC and read checks passing.

Over the last 24 hours we completed 60 checks from Tokyo and 60 answered cleanly, 100.00% availability.

Of the 3 other regions we check Splunk from, all 3 read checks passing right now.

Email me when Splunk reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Splunk's own statement from its status page, with our regional reading beside it.

What our Tokyo probe measured

TokyoChecks passing60 checks in 24h, 100.00%

Last checked Nov 5, 2026, 3:03 PM UTC.

Splunk from Tokyo over the last 30 days

Over the last 30 days, Splunk answered our Tokyo probe in 1,764 ms on average, and 1 check in 20 took longer than 2,764 ms.

Ranked by average response time across the 4 cities we check Splunk from, Tokyo 4th; Frankfurt was fastest at 802 ms and Tokyo slowest at 1,764 ms.

From Tokyo we ran 182 checks of Splunk in 4 days, and 182 answered cleanly: 100.00% availability.

Every one of those days was clean: not one failed check.

In Tokyo local time (GMT+9), Splunk was slowest around 10 AM, at 2,105 ms on average over the last 14 days, and quickest around 9 PM, at 1,164 ms.

Day (UTC)ChecksAvailabilityAverage response
Thu, Nov 537100.00%1,806 ms
Wed, Nov 459100.00%1,780 ms
Tue, Nov 359100.00%1,764 ms
Mon, Nov 227100.00%1,675 ms

Splunk outages measured from Japan

Our Tokyo probe measured no confirmed Splunk outage in the last 90 days.

How the other regions read right now

Of the 3 other regions we check Splunk from, all 3 read checks passing right now.

Probe cityRight nowLast 24h
AshburnChecks passing100.00% of 141 checks
San JoseChecks passing100.00% of 113 checks
FrankfurtChecks passing100.00% of 99 checks

Other countries we check Splunk from

How we measured this

Japan readings on this page come from RealUptime's own Tokyo probe 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.

Japan 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 Tokyo

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 servers

Run 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