Current live snapshot for this third-party public VPN endpoint: recent median speed, observed latency, last successful check, protocol and OpenVPN download action. Historical checks are shown separately when the stored history is reliable.
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 | 220.118.173.198 |
|---|---|
| proto | tcp |
| port | 995 |
| country | South Korea |
| last checked | Jul 23, 2026 11:00 UTC |
| source | VPNGate |
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 live snapshot plus stored check history when reliable history exists. The latest successful check for this endpoint is Jul 23, 2026 11:00 UTC, and the endpoint was first seen Jul 23, 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.
Check history details
Each row records a stored monitoring pass or the current live snapshot when the stored history is behind the latest check. Two consecutive failed checks deactivate an active endpoint. Inactive endpoints are retried after 72 hours, and five consecutive failed history checks remove the endpoint and its stored history. A successful check resets the failure sequence and can return an inactive endpoint to the public catalog.
| Status | Checked | Source | Speed | Ping | TTT | Failures |
|---|---|---|---|---|---|---|
| OK | Jul 23, 2026 11:00 UTC | Stored history | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Jul 20, 2026 10:43 UTC | Stored history | 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.