A VPN server in Japan, and what a Tokyo exit actually does

Japan is an archipelago at the far end of two long cable systems, so the first thing worth knowing about a Tokyo exit is arithmetic rather than marketing. Signal in fibre covers around 200 km per millisecond, and a round trip pays the distance twice, so a thousand kilometres of cable is about ten milliseconds there and back. Cable is the operative word: a route follows landing stations and rights of way, not the line you would draw on a map, and in Japan's case it often follows the coast.

Applied to Tokyo, that produces a usable table. Tokyo to Osaka is a few hundred kilometres of domestic fibre, so the floor lands in the single digits. Tokyo to Seoul is roughly 1,300 cable kilometres, a floor around 13 ms; Tokyo to Taipei is nearer 2,100 km, so about 21 ms. Tokyo to the US West Coast is around 9,000 km of Pacific cable, putting the floor near 90 ms. Tokyo to western Europe runs past 11,000 km whichever way it goes, which is why the Japanese exit is the wrong choice for a European working day.

Treat every figure above as a floor, not a forecast. The number you measure sits higher, because routers, a congested evening link and the last stretch of radio or copper are all added on top. The reason to know the floor anyway is that it separates what a subscription can change from what it cannot.

The part software does influence is the handshake — the exchanges spent agreeing keys before any real data moves. WireGuard needs one round trip for that, so starting the tunnel costs a single trip out to Tokyo. On a domestic Japanese connection that is a few milliseconds nobody notices. On a trans-Pacific path it is the difference between a connection that is up before you look at the screen and one that visibly thinks about it, and it is the reason the reconnection after a train tunnel is not an event.

Tokyo is an interconnection point and not merely a large city. Several substantial exchanges operate there — JPIX, JPNAP and BBIX among them — and the content caches, hosting providers, mobile networks and large domestic carriers that serve Japanese users keep equipment in the same handful of buildings. A packet surfacing in Tokyo is usually one peering hop from a Japanese destination instead of two or three, which is the real reason a domestic exit feels cheap to leave running.

That density reaches outward as well. From a Korean or Taiwanese network the path into Tokyo is frequently direct, so Tokyo can be the sensible exit for a reader who is not in Japan at all. Singapore plays the same role for much of Southeast and South Asia, and WrapVPN runs a Singapore region too, so from Jakarta or Manila that is usually the better of the two.

The conclusion worth carrying away: nearest on the map and nearest on the network are different claims, and only the second one decides anything. Peering is a property of your ISP rather than your country, so two people in the same Tokyo ward on different providers can read meaningfully different figures for the same exit.

Tokyo's second role comes from the cables. Trans-Pacific systems land in Chiba and Mie prefectures, a short terrestrial leg away, which is what makes Tokyo the natural turning point for traffic between East Asia and North America. So a Tokyo exit costs a reader whose destinations sit in East Asia or the United States very little, and costs a reader whose destinations are all European the long Eurasian leg out and back again.

Public Wi-Fi in Japan is easy to find and mostly open. Business hotels print one shared password on a card at reception, so every guest in the building holds the same key — the network is protected in the sense that the lobby door is locked, not in the sense that the person in the next room cannot see your traffic. Many Japanese business hotels still leave a wired LAN socket in the room, which is a habit worth keeping: a cable is usually quicker than the shared radio and it cannot be listened to from the corridor. What it does not change is what the hotel's own equipment carries, and that is the half a tunnel is for.

Convenience-store and station Wi-Fi is typically free and gated by a captive portal: you join, a page opens, you supply an email address or tap an agreement, and you are online for a fixed window before being asked again. Trains add their own rhythm — Shinkansen and many JR lines carry free Wi-Fi that drops in tunnels and between base stations, several times an hour on a long run.

Order matters on all of these. Clear the portal first, because the portal has to intercept an ordinary request in order to show you its page, and a tunnel that is already up will stop it appearing at all. Then bring the tunnel up and leave it there. Recovering after a tunnel or a handover costs that one round trip to Tokyo, which is why the drop tends to be something you notice in the status bar rather than in what you were doing.

For a trip rather than a life, how you are billed matters as much as how you connect: WrapVPN is $1.99 a week or $3.99 a month, with a $0.99 day pass and a 7-day free trial on the monthly plan, and there is no annual subscription or long-term commitment waiting to be unwound after you fly home.

Names are resolved inside the tunnel, and the ones belonging to advertising and tracking hosts are refused there, so the request is dropped at lookup instead of being fetched and then hidden. The visible effect is fewer connections opened per page, and it scales with how many third parties a page invites rather than with where you happen to be standing. A portal or aggregator front page that reaches out to dozens of separate hosts shows the difference plainly; a single-host app screen barely shows it at all.

The limit deserves stating plainly. A filter that works on names cannot separate two things served from one hostname, so an advert delivered from the same domain as the article it sits in will still arrive, and the space reserved for one that was blocked may stay blank rather than closing up. This is a network filter, not a page rewriter.

There is a travel-specific payoff. Rented pocket Wi-Fi and travel eSIMs in Japan are usually sold with a daily allowance, and background requests to hosts you never wanted spend that allowance just as effectively as the page you asked for.

Because peering is personal to your connection, the honest way to choose is to look rather than reason. Connect to Japan, read the latency the region list reports, then connect to the next nearest region and read that. If the two read close together, let the destination settle it instead of the millisecond count.

The free tier is enough to run that test properly without deciding anything first: three hours a week, a one-hour session limit and two devices, which comfortably covers an evening in a hotel and a morning at the station. The 7-day trial covers a short trip end to end.

One account covers iPhone, iPad, Mac and Android, with Windows in review, so the phone you test on in Tokyo and the laptop you work from afterwards are the same subscription rather than two decisions.