Skip to content

Outage tracker / Zwift / In Japan

Is Zwift down in Japan?

Vendor reports no incidentWhat Zwift reports

Zwift reports no incident on its status page.

As of the last successful poll, 2026-11-05 17:59 UTC.

Zwift'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 Zwift at Nov 5, 2026, 5:37 PM UTC and read checks passing.

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

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

Email me when Zwift 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 Zwift's own statement from its status page, with our regional reading beside it.

What our Tokyo probe measured

TokyoChecks passing56 checks in 24h, 100.00%

Last checked Nov 5, 2026, 5:37 PM UTC.

Zwift from Tokyo over the last 30 days

Over the last 30 days, Zwift answered our Tokyo probe in 2,881 ms on average, and 1 check in 20 took longer than 4,681 ms.

Ranked by average response time across the 4 cities we check Zwift from, Tokyo 4th; Ashburn was fastest at 969 ms and Tokyo slowest at 2,881 ms.

From Tokyo we ran 176 checks of Zwift in 4 days, and 175 answered cleanly: 99.43% availability.

1 of the 4 days had at least one failed check. The weakest was Nov 4 (UTC), at 98.14% across 54 checks.

In Tokyo local time (GMT+9), Zwift was slowest around 8 PM, at 4,037 ms on average over the last 14 days, and quickest around 5 PM, at 2,057 ms.

Day (UTC)ChecksAvailabilityAverage response
Thu, Nov 542100.00%3,690 ms
Wed, Nov 45498.14%3,611 ms
Tue, Nov 356100.00%1,870 ms
Mon, Nov 224100.00%2,189 ms

Zwift outages measured from Japan

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

How the other regions read right now

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

Probe cityRight nowLast 24h
AshburnChecks passing100.00% of 138 checks
San JoseChecks passing100.00% of 103 checks
FrankfurtChecks passing100.00% of 93 checks

Other countries we check Zwift from

How we measured this

Japan readings on this page come from RealUptime's own Tokyo probe against Zwift's public endpoints. They are not user reports, and they are not Zwift's own status page.

See Zwift'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 Zwift 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