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 | 126.89.189.161 |
|---|---|
| proto | udp |
| port | 1444 |
| country | Japan |
| last checked | Sep 10, 2026 16:32 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 10, 2026 16:32 UTC, and the endpoint was first seen no later than Sep 7, 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 10, 2026 16:32 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Sep 10, 2026 16:17 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| OK | Sep 10, 2026 16:17 UTC | 3.5 Mbps | 274 ms | 2681 ms | 0 |
| OK | Sep 9, 2026 17:16 UTC | 3.5 Mbps | 275 ms | 2512 ms | 0 |
| OK | Sep 9, 2026 14:08 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 8, 2026 18:15 UTC | 3.6 Mbps | 269 ms | 2509 ms | 0 |
| OK | Sep 7, 2026 18:15 UTC | 3.5 Mbps | 272 ms | 3068 ms | 0 |
| Fail | Sep 7, 2026 17:07 UTC | Unknown Mbps | Unknown ms | Unknown ms | 4 |
| Fail | Sep 7, 2026 15:51 UTC | Unknown Mbps | Unknown ms | Unknown ms | 3 |
| Fail | Sep 7, 2026 14:26 UTC | Unknown Mbps | Unknown ms | Unknown ms | 2 |
| Fail | Sep 7, 2026 14:11 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| Fail | Sep 6, 2026 14:17 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 5, 2026 14:16 UTC | 3.2 Mbps | 275 ms | 2513 ms | 0 |
| OK | Sep 4, 2026 14:14 UTC | 2.8 Mbps | 276 ms | 2466 ms | 0 |
| OK | Sep 4, 2026 14:11 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 3, 2026 14:13 UTC | 3.4 Mbps | 276 ms | 2838 ms | 0 |
| OK | Sep 2, 2026 14:12 UTC | 3.2 Mbps | 269 ms | 2393 ms | 0 |
| OK | Sep 1, 2026 14:10 UTC | 3.5 Mbps | 272 ms | 2535 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.