🇯🇵 Japan
Tunnel checked - metrics pending Recent 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 14:35 UTC. The endpoint is not shown as live because speed or latency is not measured. Download is disabled until a new successful check and configuration validation pass.
Network score19/100Not a privacy or operator-trust score
Checker result: throughput1.5 Mbpssuspect
Checker result: tunnel RTT501 mssuspect
Reported by source: speedNot reported
Reported by source: pingNot reported
Protocol / portTCP 443
AvailabilityTunnel checked - metrics pending
Successful checks shown10 / 20
Consecutive failed checks0 / 10
Last checked5 h ago
IP219.100.37.199
First seenAug 30, 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.199 |
|---|---|
| proto | tcp |
| port | 443 |
| country | Japan |
| last checked | Sep 10, 2026 14:35 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 14:35 UTC, and the endpoint was first seen no later than Aug 30, 2026.
Check rows shown10 successful checks out of 20
Recent speednot measured
Recent latencynot measured
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.
OK
UnknownMbps
UnknownPing ms
UnknownTTT ms
0Failures
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
UnknownMbps
UnknownPing ms
UnknownTTT ms
0Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
1Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
0Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
0Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
0Failures
OK
UnknownMbps
UnknownPing ms
UnknownTTT ms
0Failures
OK
1.5Mbps
501Ping ms
4405TTT ms
0Failures
OK
0.5Mbps
539Ping ms
4511TTT ms
0Failures
OK
2.3Mbps
425Ping ms
3459TTT ms
0Failures
OK
UnknownMbps
UnknownPing ms
UnknownTTT ms
0Failures
OK
0.9Mbps
357Ping ms
7541TTT ms
0Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
0Failures
OK
0.7Mbps
356Ping ms
7378TTT ms
0Failures
Fail
UnknownMbps
UnknownPing ms
UnknownTTT ms
2Failures
| Status | Checked | Speed | Ping | TTT | Failures |
|---|---|---|---|---|---|
| OK | Sep 10, 2026 14:35 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Sep 10, 2026 14:21 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| Fail | Sep 10, 2026 14:20 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| Fail | Sep 9, 2026 17:04 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 9, 2026 15:19 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Sep 8, 2026 18:02 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 8, 2026 15:51 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Sep 8, 2026 15:36 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| Fail | Sep 7, 2026 18:00 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Sep 6, 2026 18:00 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Sep 5, 2026 17:59 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 5, 2026 15:36 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 4, 2026 17:56 UTC | 1.5 Mbps | 501 ms | 4405 ms | 0 |
| OK | Sep 3, 2026 17:55 UTC | 0.5 Mbps | 539 ms | 4511 ms | 0 |
| OK | Sep 2, 2026 15:39 UTC | 2.3 Mbps | 425 ms | 3459 ms | 0 |
| OK | Sep 2, 2026 15:36 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 1, 2026 15:38 UTC | 0.9 Mbps | 357 ms | 7541 ms | 0 |
| Fail | Aug 31, 2026 15:37 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Aug 30, 2026 15:35 UTC | 0.7 Mbps | 356 ms | 7378 ms | 0 |
| Fail | Aug 30, 2026 14:52 UTC | Unknown Mbps | Unknown ms | Unknown ms | 2 |
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