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 | 202.157.252.10 |
|---|---|
| proto | tcp |
| port | 1734 |
| country | Japan |
| last checked | Sep 5, 2026 13:16 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 5, 2026 13:16 UTC, and the endpoint was first seen no later than Aug 13, 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 stored and are retried until a later successful tunnel check returns them to the catalog.
| Status | Checked | Speed | Ping | TTT | Failures |
|---|---|---|---|---|---|
| Fail | Sep 7, 2026 11:02 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Sep 6, 2026 11:01 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 5, 2026 13:16 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Sep 5, 2026 13:01 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| OK | Sep 5, 2026 10:59 UTC | 3.5 Mbps | 251 ms | 2824 ms | 0 |
| OK | Sep 4, 2026 10:58 UTC | 3.6 Mbps | 245 ms | 3192 ms | 0 |
| OK | Sep 3, 2026 10:57 UTC | 3.5 Mbps | 242 ms | 3015 ms | 0 |
| OK | Sep 2, 2026 13:01 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 2, 2026 10:56 UTC | 3.6 Mbps | 243 ms | 2867 ms | 0 |
| OK | Sep 1, 2026 10:54 UTC | Unknown Mbps | 658 ms | 6577 ms | 0 |
| OK | Aug 31, 2026 10:53 UTC | 0.9 Mbps | 246 ms | 3558 ms | 0 |
| OK | Aug 30, 2026 13:00 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Aug 30, 2026 10:48 UTC | 3.7 Mbps | 250 ms | 2935 ms | 0 |
| OK | Aug 29, 2026 10:46 UTC | 3.6 Mbps | 251 ms | 3015 ms | 0 |
| OK | Aug 28, 2026 10:27 UTC | 3.7 Mbps | 238 ms | 3092 ms | 0 |
| OK | Aug 27, 2026 13:00 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Aug 27, 2026 10:26 UTC | 3.5 Mbps | 241 ms | 2961 ms | 0 |
| Fail | Aug 26, 2026 10:24 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.