Current live snapshot for this third-party public VPN endpoint: measured speed, observed latency, last successful check, protocol and OpenVPN download action. Historical checks are shown separately when the stored history is reliable.
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 Jun 1, 2026 21:52 UTC, and the endpoint was first seen May 20, 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.
This endpoint is compared with 1606 other live checked Japan OpenVPN rows in the current catalog.
OpenVPN config
Technical check ≠ privacy guarantee
This card describes one public OpenVPN endpoint from the checked catalog. The profile is supplied by a third-party source; PublicVPNList stores the parsed endpoint, the latest measurements and the recent check history so users can compare it before downloading.
| Country | Japan |
|---|---|
| Host | 60.56.148.72 |
| IP | 60.56.148.72 |
| Protocol and port | TCP / 1449 |
| Source | AutoOVPN |
| Current snapshot check | Jun 1, 2026 21:52 UTC |
Use this public OpenVPN endpoint for temporary testing, route comparison or low-risk browsing after reviewing the .ovpn profile. Latency is low in the latest snapshot, so it is a better candidate for interactive tests than slower regional alternatives. The last check is older than two hours, so run the live test before downloading.
Detailed history may lag behind the latest live snapshot.
Each row records a stored monitoring pass. The current live snapshot above may be newer than this detailed history. If this server fails 10 consecutive checks, the VPN element is deactivated and disappears from public tables, downloads and country pages until a later successful response.
| Status | Checked | Speed | Ping | TTT | Failures |
|---|---|---|---|---|---|
| OK | May 29, 2026 06:29 UTC | — Mbps | — ms | — ms | 0 |
| OK | May 29, 2026 06:28 UTC | — Mbps | 227 ms | 524 ms | 0 |
| OK | May 29, 2026 06:28 UTC | — Mbps | 234 ms | 524 ms | 0 |
| OK | May 29, 2026 06:28 UTC | — Mbps | 243 ms | 524 ms | 0 |
| OK | May 29, 2026 06:28 UTC | — Mbps | 226 ms | 524 ms | 0 |
| OK | May 29, 2026 06:28 UTC | — Mbps | 205 ms | 524 ms | 0 |
| OK | May 20, 2026 10:54 UTC | 5.7 Mbps | 303 ms | 3261 ms | 0 |
Prefer this server when the current availability is stable, the measured speed and observed latency fit your region, and the last successful check is recent. Use TCP for restrictive networks and UDP for lower overhead when your connection allows it. Public VPN servers are third-party endpoints, so inspect the downloaded .ovpn file and avoid sensitive traffic on unknown infrastructure.
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.