🇯🇵 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 11, 2026 20:13 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 score32/100Not a privacy or operator-trust score
Measured by PublicVPNList: throughput0.6 MbpsSep 10, 2026 21:12 UTC
Measured by PublicVPNList: tunnel RTT253 msopenvpn_tunnel_recovery_v1
Reported by source: speedNot reported
Reported by source: pingNot reported
Protocol / portTCP 443
AvailabilityActive - not yet verified
Successful checks shown5 / 20
Consecutive failed checks1 / 10
Last checked4 min ago
IP219.100.37.224
First seenSep 10, 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.224 |
|---|---|
| proto | tcp |
| port | 443 |
| country | Japan |
| last checked | Sep 11, 2026 20:13 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 11, 2026 20:13 UTC, and the endpoint was first seen no later than Sep 10, 2026.
Check rows shown5 successful checks out of 20
Recent speedcurrent checker snapshot 0.6 Mbps
Recent latencycurrent checker snapshot 253 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
OK
0.6Mbps
253Ping ms
3616TTT ms
0Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
4Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
3Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
2Failures
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
OK
0.3Mbps
272Ping ms
3593TTT ms
0Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
2Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
1Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
0Failures
OK
1.5Mbps
473Ping ms
4746TTT ms
0Failures
OK
1.7Mbps
268Ping ms
7816TTT ms
0Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
3Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
2Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
1Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
0Failures
| Status | Checked | Speed | Ping | TTT | Failures |
|---|---|---|---|---|---|
| Fail | Sep 11, 2026 20:14 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| Fail | Sep 11, 2026 20:13 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| OK | Sep 10, 2026 21:12 UTC | 0.6 Mbps | 253 ms | 3616 ms | 0 |
| Fail | Sep 10, 2026 17:40 UTC | Unknown Mbps | Unknown ms | Unknown ms | 4 |
| Fail | Sep 10, 2026 15:26 UTC | Unknown Mbps | Unknown ms | Unknown ms | 3 |
| Fail | Sep 10, 2026 15:06 UTC | Unknown Mbps | Unknown ms | Unknown ms | 2 |
| Fail | Sep 10, 2026 14:53 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| Fail | Sep 10, 2026 14:51 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| Fail | Sep 9, 2026 15:50 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 9, 2026 15:49 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 8, 2026 16:35 UTC | 0.3 Mbps | 272 ms | 3593 ms | 0 |
| Fail | Sep 8, 2026 16:18 UTC | Unknown Mbps | Unknown ms | Unknown ms | 2 |
| Fail | Sep 8, 2026 16:03 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| Fail | Sep 7, 2026 16:05 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 6, 2026 16:04 UTC | 1.5 Mbps | 473 ms | 4746 ms | 0 |
| OK | Sep 5, 2026 16:02 UTC | 1.7 Mbps | 268 ms | 7816 ms | 0 |
| Fail | Sep 5, 2026 12:10 UTC | Unknown Mbps | Unknown ms | Unknown ms | 3 |
| Fail | Sep 5, 2026 11:52 UTC | Unknown Mbps | Unknown ms | Unknown ms | 2 |
| Fail | Sep 5, 2026 11:37 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| Fail | Sep 4, 2026 12:11 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 · 3.5 Mbps · 265 ms · UDP 1437 · 124.44.47.30
🇯🇵 Japan · 3.5 Mbps · 270 ms · TCP 1734 · 202.157.252.10
🇯🇵 Japan · 3.5 Mbps · 263 ms · UDP 1645 · 124.18.151.84
🇯🇵 Japan · 3.5 Mbps · 276 ms · UDP 1648 · 60.137.217.108
🇯🇵 Japan · 3.5 Mbps · 241 ms · TCP 1462 · 183.86.87.204