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 | 114.183.172.26 |
|---|---|
| proto | tcp |
| port | 1917 |
| country | Japan |
| last checked | Sep 11, 2026 12:48 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 11, 2026 12:48 UTC, and the endpoint was first seen no later than Aug 29, 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 11, 2026 12:48 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Sep 11, 2026 08:01 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 10, 2026 13:47 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Sep 10, 2026 09:00 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 9, 2026 14:47 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 9, 2026 10:00 UTC | 1.6 Mbps | 391 ms | 3641 ms | 0 |
| OK | Sep 8, 2026 10:00 UTC | 2.2 Mbps | 394 ms | 3631 ms | 0 |
| OK | Sep 7, 2026 09:59 UTC | 2.4 Mbps | 383 ms | 3783 ms | 0 |
| OK | Sep 7, 2026 09:46 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 6, 2026 09:59 UTC | 2.3 Mbps | 392 ms | 3739 ms | 0 |
| OK | Sep 5, 2026 09:57 UTC | 2 Mbps | 390 ms | 4118 ms | 0 |
| OK | Sep 4, 2026 09:56 UTC | 2.1 Mbps | 402 ms | 3780 ms | 0 |
| OK | Sep 4, 2026 09:46 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 3, 2026 09:53 UTC | 2.1 Mbps | 382 ms | 3713 ms | 0 |
| OK | Sep 2, 2026 09:52 UTC | 2.3 Mbps | 380 ms | 3688 ms | 0 |
| OK | Sep 1, 2026 09:50 UTC | 2.3 Mbps | 381 ms | 3633 ms | 0 |
| OK | Sep 1, 2026 09:46 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Aug 31, 2026 09:49 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Aug 30, 2026 09:46 UTC | 2.3 Mbps | 407 ms | 3795 ms | 0 |
| OK | Aug 29, 2026 09:45 UTC | 2.3 Mbps | 387 ms | 3585 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.