Free VPN servers in Japan

418 Japan servers answered a handshake within the last five minutes. The list re-ranks after every probe round — fastest and steadiest first.

418
Alive now
26 ms
Average latency
100
Best score
376
Downloaded
🇯🇵 JapanJP · 418 alive of 2,415 tracked here
#
IP address
Proto
Latency
Uptime 7d
Downloads
Score
Checked
351
TCP/130815 ms52.6%—
54
4m ago
Details
352
TCP/174613 ms41.2%—
54
4m ago
Details
353
TCP/134610 ms40.3%—
53
4m ago
Details
354
TCP/19448 ms40.1%—
53
4m ago
Details
355
TCP/161610 ms40.1%—
53
4m ago
Details
356
TCP/17247 ms39.8%—
53
4m ago
Details
357
TCP/124626 ms37.9%18
53
4m ago
Details
358
TCP/17478 ms37.9%—
53
4m ago
Details
359
TCP/194720 ms37.3%—
53
4m ago
Details
360
TCP/16917 ms37.2%—
53
4m ago
Details
361
TCP/12846 ms36.0%—
52
4m ago
Details
362
TCP/153510 ms84.9%—
52
4m ago
Details
363
TCP/178712 ms35.7%—
52
4m ago
Details
364
TCP/144815 ms35.6%—
52
4m ago
Details
365
TCP/167911 ms35.5%—
52
4m ago
Details
366
TCP/169125 ms35.2%—
52
4m ago
Details
367
TCP/134617 ms35.2%—
52
4m ago
Details
368
TCP/18356 ms36.4%—
52
4m ago
Details
369
TCP/175813 ms38.4%—
52
4m ago
Details
370
TCP/137723 ms34.4%—
52
4m ago
Details
371
TCP/19079 ms32.7%—
52
4m ago
Details
372
UDP/11958 ms60.1%—
52
4m ago
Details
373
TCP/149512 ms38.0%—
52
4m ago
Details
374
TCP/182215 ms43.3%—
52
4m ago
Details
375
TCP/18338 ms31.4%—
52
4m ago
Details
376
TCP/147235 ms39.0%—
52
4m ago
Details
377
TCP/17049 ms29.7%—
51
4m ago
Details
378
TCP/15628 ms29.6%—
51
4m ago
Details
379
TCP/149610 ms28.4%—
51
4m ago
Details
380
TCP/194014 ms27.5%—
51
4m ago
Details
381
TCP/160110 ms25.4%—
51
4m ago
Details
382
TCP/142513 ms33.0%—
51
4m ago
Details
383
TCP/168110 ms24.2%—
51
4m ago
Details
384
TCP/155410 ms34.6%—
51
4m ago
Details
385
TCP/134613 ms23.3%—
51
4m ago
Details
386
TCP/196910 ms22.7%—
51
4m ago
Details
387
TCP/192912 ms46.3%—
51
4m ago
Details
388
TCP/17806 ms24.1%—
51
4m ago
Details
389
TCP/132419 ms47.2%—
50
4m ago
Details
390
TCP/171720 ms20.3%—
50
4m ago
Details
391
TCP/167313 ms20.3%1
50
4m ago
Details
392
TCP/17165 ms39.1%—
50
4m ago
Details
393
TCP/17068 ms28.7%—
50
4m ago
Details
394
TCP/18178 ms19.0%—
50
4m ago
Details
395
TCP/183817 ms60.0%—
50
4m ago
Details
396
TCP/144317 ms14.5%2
50
4m ago
Details
397
TCP/126613 ms19.9%—
50
4m ago
Details
398
TCP/189616 ms13.3%—
50
4m ago
Details
399
TCP/18594 ms23.2%—
50
4m ago
Details
400
TCP/198423 ms12.5%—
50
4m ago
Details
Showing 351–400 of 418

What these numbers say about Japan

We have collected 2,415 servers in Japan in total, and 418 of them answered a real OpenVPN handshake within the last five minutes — 76 over UDP and 342 over TCP. The quickest replied in 4 ms, against a country average of 26 ms. Over the past seven days the ones still standing have answered 71.3% of the probes we sent them.

Between the two protocols: UDP is faster and is the right default on a fixed connection, while the 342 TCP entries are the safer pick on mobile data or behind a firewall, because carriers and corporate networks drop idle UDP long before they interfere with TCP. The ports most of them listen on here are 443, 1195, 1716 — 443 is the one least likely to be blocked on a restrictive network, so start there if you are behind a corporate or campus firewall. Once you have picked one, the iPhone, Android and desktop guides each take about two minutes.

5 of the live Japan servers are ones we first saw in the last twenty-four hours. That churn is normal and not a defect: these are volunteer machines that get added, moved and switched off without notice, which is precisely why the list is rebuilt every hour instead of being curated once. How the score is built has the formula in full.

Two things these figures deliberately do not claim. The latency is measured from our prober, which sits in one fixed place — it ranks Japan servers against each other honestly, but it is not a prediction of your own ping. If you are closer to Japan than our prober is, yours will be lower than the number shown. And a handshake proves an OpenVPN daemon is listening; it says nothing about whether that machine's own connection is healthy, and nothing at all about who runs it or what they can see.