🇯🇵 Japan
Active - not yet verified Fresh Source: AutoOVPN
Current snapshot for this third-party public VPN endpoint: checker throughput and tunnel RTT when available, last successful check, protocol and OpenVPN download status. Source-reported and stored historical values are shown separately.
Inactive — did not pass verification
Last successful check: Sep 10, 2026 13:11 UTC. The endpoint is not shown as live because latest check failed. Download is disabled until a new successful check and configuration validation pass.
Network score35/100Not a privacy or operator-trust score
Measured by PublicVPNList: throughput2.0 MbpsSep 8, 2026 12:19 UTC
Measured by PublicVPNList: tunnel RTT493 msopenvpn_tunnel_metrics_v1
Reported by source: speedNot reported
Reported by source: pingNot reported
Protocol / portTCP 443
AvailabilityActive - not yet verified
Successful checks shown14 / 20
Consecutive failed checks1 / 10
Last checked5 min ago
IP219.100.37.21
First seenAug 9, 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 | 219.100.37.21 |
|---|---|
| proto | tcp |
| port | 443 |
| country | Japan |
| last checked | Sep 10, 2026 13:11 UTC |
| source | AutoOVPN |
Safety note
TCP 443 safety note
TCP 443 can be useful on restrictive networks, but it is not a privacy guarantee and it is not invisible. Treat it as a connectivity option, not as proof that the VPN operator is trustworthy. Compare freshness, latency and score before downloading, then verify IP and DNS after connecting.
Server evidence summary
This detail page is built from the current published snapshot. The latest successful check for this endpoint is Sep 10, 2026 13:11 UTC, and the endpoint was first seen no later than Aug 9, 2026.
Check rows shown14 successful checks out of 20
Recent speedcurrent checker snapshot 2.0 Mbps
Recent latencycurrent checker snapshot 493 ms
Source provenanceAutoOVPN
Country speed comparisonFaster than 0%
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.
Hover, focus or tap a point for check details.
Hover, focus or tap a point for check details.
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 on the site with their check status and are retried. A later successful check can return them to the working list.
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
1Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
1Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
0Failures
OK
UnknownMbps
UnknownPing ms
UnknownTTT ms
0Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
0Failures
OK
2.0Mbps
493Ping ms
6838TTT ms
0Failures
OK
UnknownMbps
UnknownPing ms
UnknownTTT ms
0Failures
OK
2.4Mbps
333Ping ms
3976TTT ms
0Failures
OK
2.9Mbps
336Ping ms
4628TTT ms
0Failures
OK
1.3Mbps
344Ping ms
3726TTT ms
0Failures
OK
UnknownMbps
UnknownPing ms
UnknownTTT ms
0Failures
OK
2.8Mbps
281Ping ms
4237TTT ms
0Failures
OK
1.6Mbps
254Ping ms
5749TTT ms
0Failures
OK
2.5Mbps
427Ping ms
4666TTT ms
0Failures
OK
UnknownMbps
UnknownPing ms
UnknownTTT ms
0Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
1Failures
OK
0.7Mbps
247Ping ms
6463TTT ms
0Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
0Failures
OK
2.4Mbps
269Ping ms
3533TTT ms
0Failures
OK
UnknownMbps
UnknownPing ms
UnknownTTT ms
0Failures
| Status | Checked | Speed | Ping | TTT | Failures |
|---|---|---|---|---|---|
| Fail | Sep 10, 2026 13:14 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| Fail | Sep 10, 2026 13:11 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| Fail | Sep 10, 2026 11:23 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 9, 2026 14:11 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Sep 9, 2026 12:21 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 8, 2026 12:19 UTC | 2.0 Mbps | 493 ms | 6838 ms | 0 |
| OK | Sep 8, 2026 11:50 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 7, 2026 12:18 UTC | 2.4 Mbps | 333 ms | 3976 ms | 0 |
| OK | Sep 6, 2026 12:17 UTC | 2.9 Mbps | 336 ms | 4628 ms | 0 |
| OK | Sep 5, 2026 12:15 UTC | 1.3 Mbps | 344 ms | 3726 ms | 0 |
| OK | Sep 5, 2026 11:50 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 4, 2026 12:14 UTC | 2.8 Mbps | 281 ms | 4237 ms | 0 |
| OK | Sep 3, 2026 12:11 UTC | 1.6 Mbps | 254 ms | 5749 ms | 0 |
| OK | Sep 2, 2026 12:06 UTC | 2.5 Mbps | 427 ms | 4666 ms | 0 |
| OK | Sep 2, 2026 11:50 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Sep 2, 2026 11:34 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| OK | Sep 1, 2026 12:05 UTC | 0.7 Mbps | 247 ms | 6463 ms | 0 |
| Fail | Aug 31, 2026 12:03 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Aug 30, 2026 11:59 UTC | 2.4 Mbps | 269 ms | 3533 ms | 0 |
| OK | Aug 30, 2026 11:34 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
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.7 Mbps · 257 ms · UDP 1338 · 58.146.63.139
🇯🇵 Japan · 3.7 Mbps · 263 ms · UDP 1645 · 124.18.151.84
🇯🇵 Japan · 3.5 Mbps · 269 ms · UDP 1437 · 124.44.47.30
🇯🇵 Japan · 3.5 Mbps · 252 ms · TCP 1734 · 202.157.252.10