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.
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.16 |
|---|---|
| proto | tcp |
| port | 443 |
| country | Japan |
| last checked | Sep 22, 2026 02:53 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 22, 2026 02:53 UTC, and the endpoint was first seen no later than Sep 3, 2026.
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.
| Status | Checked | Speed | Ping | TTT | Failures |
|---|---|---|---|---|---|
| OK | Sep 22, 2026 02:53 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Sep 22, 2026 02:38 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| Fail | Sep 22, 2026 02:37 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| Fail | Sep 21, 2026 03:37 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 21, 2026 03:36 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 20, 2026 04:36 UTC | 0.1 Mbps | 293 ms | 7045 ms | 0 |
| OK | Sep 19, 2026 05:50 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Sep 19, 2026 05:35 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| Fail | Sep 19, 2026 05:34 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| OK | Sep 18, 2026 06:33 UTC | 0.1 Mbps | 248 ms | 4683 ms | 0 |
| Fail | Sep 18, 2026 06:31 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| OK | Sep 17, 2026 07:31 UTC | Unknown Mbps | 261 ms | 8099 ms | 0 |
| Fail | Sep 17, 2026 07:30 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| OK | Sep 16, 2026 08:29 UTC | 0.1 Mbps | 253 ms | 4840 ms | 0 |
| OK | Sep 16, 2026 08:26 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Sep 15, 2026 09:27 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 15, 2026 09:26 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 14, 2026 10:26 UTC | 0.6 Mbps | 385 ms | 4177 ms | 0 |
| OK | Sep 13, 2026 11:40 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Sep 13, 2026 11:25 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
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.