🇯🇵 Japan
Full-tunnel verified Recent Recent Source: AutoOVPN
Live checked and technically verified. This config passed a full-tunnel HTTPS check and changed the checker's public exit IP. Current throughput, tunnel RTT, last successful check and OpenVPN download action are shown below. This technical check does not verify the third-party operator or privacy policy.
Limited or Stale server evidence
This endpoint remains available for reference, but it is marked noindex,follow and excluded from the stable-server sitemap until it has sufficient age, successful checks, recent confirmation and an acceptable success rate.
Network score24/100Not a privacy or operator-trust score
Measured by PublicVPNList: throughput4 MbpsSep 6, 2026 21:35 UTC
Measured by PublicVPNList: tunnel RTT244 msopenvpn_tunnel_recovery_v1
Reported by source: speedNot reported
Reported by source: pingNot reported
Protocol / portUDP 1973
AvailabilityRecent
Successful checks shown1 / 20
Consecutive failed checks0 / 10
Last checked1 d ago
IP59.86.118.137
First seenSep 6, 2026
SourceAutoOVPN
How the network score is calculated
This score compares current usability signals:
- Freshness: how recently the endpoint passed a check
- Speed: latest measured throughput
- Latency: round-trip time from the checker location
- Stability: recent successful and failed checks
- Config availability: whether a downloadable profile exists
Not a privacy or operator-trust score. It does not verify the VPN operator, logging policy, jurisdiction or traffic handling.
Expected .ovpn profile fields
Before importing the downloaded profile, compare these visible endpoint fields with the remote, proto and port values inside the file.
| remote | 59.86.118.137 |
|---|---|
| proto | udp |
| port | 1973 |
| country | Japan |
| last checked | Sep 6, 2026 21:35 UTC |
| source | AutoOVPN |
Safety note
Public VPN safety note
Public VPN servers can be useful for testing routes, ports and OpenVPN client setup, but a successful technical check does not verify the operator, logging policy, jurisdiction or long-term privacy. Avoid sensitive accounts and review the .ovpn profile before connecting.
Server evidence summary
This detail page is built from the current published snapshot. The latest successful check for this endpoint is Sep 6, 2026 21:35 UTC, and the endpoint was first seen no later than Sep 6, 2026.
Check rows shown1 successful checks out of 20
Recent speedcurrent checker snapshot 4 Mbps
Recent latencycurrent checker snapshot 244 ms
Source provenanceAutoOVPN
Country speed comparisonFaster than 100%
Country latency rank#12 of 1831
PublicVPNList stores the parsed endpoint, protocol, port, source label and measurement results so users can compare this server before downloading. The source label describes where the public profile was discovered; it does not prove who operates the VPN endpoint or what logging policy it follows.
Check history details
Recent checks are shown below. Rows labelled “current snapshot” show the latest published state; the other rows are saved check results. A failure counter describes consecutive failures, not the total number of failed rows shown here. Repeated failures deactivate an endpoint; inactive endpoints remain stored and are retried until a later successful tunnel check returns them to the catalog.
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
0Failures
OK
4Mbps
244Ping ms
2715TTT ms
0Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
27Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
26Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
25Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
24Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
23Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
22Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
21Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
20Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
19Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
18Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
17Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
16Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
15Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
14Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
13Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
12Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
11Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
10Failures
| Status | Checked | Speed | Ping | TTT | Failures |
|---|---|---|---|---|---|
| Fail | Sep 7, 2026 21:36 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 6, 2026 21:35 UTC | 4 Mbps | 244 ms | 2715 ms | 0 |
| Fail | Sep 6, 2026 13:48 UTC | Unknown Mbps | Unknown ms | Unknown ms | 27 |
| Fail | Sep 6, 2026 07:02 UTC | Unknown Mbps | Unknown ms | Unknown ms | 26 |
| Fail | Sep 5, 2026 23:41 UTC | Unknown Mbps | Unknown ms | Unknown ms | 25 |
| Fail | Sep 5, 2026 17:00 UTC | Unknown Mbps | Unknown ms | Unknown ms | 24 |
| Fail | Sep 5, 2026 08:57 UTC | Unknown Mbps | Unknown ms | Unknown ms | 23 |
| Fail | Sep 5, 2026 01:24 UTC | Unknown Mbps | Unknown ms | Unknown ms | 22 |
| Fail | Sep 4, 2026 19:13 UTC | Unknown Mbps | Unknown ms | Unknown ms | 21 |
| Fail | Sep 4, 2026 11:34 UTC | Unknown Mbps | Unknown ms | Unknown ms | 20 |
| Fail | Sep 4, 2026 03:57 UTC | Unknown Mbps | Unknown ms | Unknown ms | 19 |
| Fail | Sep 3, 2026 21:47 UTC | Unknown Mbps | Unknown ms | Unknown ms | 18 |
| Fail | Sep 3, 2026 14:31 UTC | Unknown Mbps | Unknown ms | Unknown ms | 17 |
| Fail | Sep 3, 2026 08:16 UTC | Unknown Mbps | Unknown ms | Unknown ms | 16 |
| Fail | Sep 3, 2026 01:16 UTC | Unknown Mbps | Unknown ms | Unknown ms | 15 |
| Fail | Sep 2, 2026 19:15 UTC | Unknown Mbps | Unknown ms | Unknown ms | 14 |
| Fail | Sep 2, 2026 07:36 UTC | Unknown Mbps | Unknown ms | Unknown ms | 13 |
| Fail | Sep 2, 2026 01:04 UTC | Unknown Mbps | Unknown ms | Unknown ms | 12 |
| Fail | Sep 1, 2026 18:40 UTC | Unknown Mbps | Unknown ms | Unknown ms | 11 |
| Fail | Sep 1, 2026 04:38 UTC | Unknown Mbps | Unknown ms | Unknown ms | 10 |
Alternative live VPN servers
Use these alternatives if this endpoint is slow from your route, the protocol is blocked, or the latest live test fails before download. Same-country alternatives preserve the location target; global alternatives prioritize measured speed and recent checks.
Live alternatives in Japan
🇯🇵 Japan · 23.4 Mbps · 3 ms · TCP 1260 · 125.4.167.98
🇯🇵 Japan · 3.8 Mbps · 250 ms · UDP 1933 · 219.122.100.216
🇯🇵 Japan · 3.7 Mbps · 259 ms · UDP 1822 · 219.113.61.64
🇯🇵 Japan · 3.7 Mbps · 263 ms · UDP 1437 · 124.44.47.30
🇯🇵 Japan · 3.5 Mbps · 251 ms · TCP 1734 · 202.157.252.10