Skip to main content

Live Checked South Korea OpenVPN server 122.128.209.73

Endpoint 122.128.209.73:1602 / TCP 28Network scoreLow confidence · not a trust score
Report dead
🇰🇷 South Korea Full-tunnel verified Recent Recent Source: MYTAdityaOVPN

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.

Network score28/100Not a privacy or operator-trust score
Measured by PublicVPNList: throughput2.1 MbpsOct 9, 2026 04:35 UTC
Measured by PublicVPNList: tunnel RTT358 msopenvpn_tunnel_recovery_v1
Reported by source: speedNot reported
Reported by source: pingNot reported
Protocol / portTCP 1602
AvailabilityRecent
Successful checks shown8 / 20
Consecutive failed checks0 / 10
Last checked1 h ago
IP122.128.209.73
First seenOct 9, 2026
SourceMYTAdityaOVPN

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.

remote122.128.209.73
prototcp
port1602
countrySouth Korea
last checkedOct 9, 2026 04:35 UTC
sourceMYTAdityaOVPN

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 Oct 9, 2026 04:35 UTC, and the endpoint was first seen no later than Oct 9, 2026.

Check rows shown8 successful checks out of 20
Recent speedcurrent checker snapshot 2.1 Mbps
Recent latencycurrent checker snapshot 358 ms
Source provenanceMYTAdityaOVPN
Country speed comparisonFaster than 46%
Country latency rank#843 of 923

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.

Advertisement

Speed history

Stored historical checks, newest on the right. This chart is separate from the current live snapshot above.

Hover, focus or tap a point for check details.

Speed (Mbps)2.21.10Oct 3Oct 7Oct 9Check date (UTC)Latest 2.1 Mbps

Latency history

Stored historical checks only. Lower observed latency is better for interactive usage.

Hover, focus or tap a point for check details.

Latency (ms)4582290Oct 3Oct 7Oct 9Check date (UTC)Latest 358 ms
Advertisement

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.

OK
2.1Mbps 358Ping ms 3540TTT ms 0Failures
Fail
UnknownMbps UnknownPing ms UnknownTTT ms 3Failures
Fail
UnknownMbps UnknownPing ms UnknownTTT ms 2Failures
Fail
UnknownMbps UnknownPing ms UnknownTTT ms 1Failures
Fail
UnknownMbps UnknownPing ms UnknownTTT ms 1Failures
OK
2.2Mbps 346Ping ms 3308TTT ms 0Failures
Fail
UnknownMbps UnknownPing ms UnknownTTT ms 2Failures
Fail
UnknownMbps UnknownPing ms UnknownTTT ms 1Failures
Fail
UnknownMbps UnknownPing ms UnknownTTT ms 1Failures
OK
0.2Mbps 458Ping ms 4690TTT ms 0Failures
Fail
UnknownMbps UnknownPing ms UnknownTTT ms 2Failures
Fail
UnknownMbps UnknownPing ms UnknownTTT ms 1Failures
Fail
UnknownMbps UnknownPing ms UnknownTTT ms 1Failures
OK
2.1Mbps 362Ping ms 3670TTT ms 0Failures
OK
UnknownMbps UnknownPing ms UnknownTTT ms 0Failures
OK
UnknownMbps 363Ping ms 3553TTT ms 0Failures
OK
UnknownMbps UnknownPing ms UnknownTTT ms 0Failures
OK
0.7Mbps 358Ping ms 3613TTT ms 0Failures
Fail
UnknownMbps UnknownPing ms UnknownTTT ms 4Failures
Fail
UnknownMbps UnknownPing ms UnknownTTT ms 3Failures
Status Checked Speed Ping TTT Failures
OK Oct 9, 2026 04:35 UTC 2.1 Mbps 358 ms 3540 ms 0
Fail Oct 9, 2026 02:29 UTC Unknown Mbps Unknown ms Unknown ms 3
Fail Oct 9, 2026 00:12 UTC Unknown Mbps Unknown ms Unknown ms 2
Fail Oct 8, 2026 23:57 UTC Unknown Mbps Unknown ms Unknown ms 1
Fail Oct 8, 2026 23:57 UTC Unknown Mbps Unknown ms Unknown ms 1
OK Oct 8, 2026 00:57 UTC 2.2 Mbps 346 ms 3308 ms 0
Fail Oct 8, 2026 00:33 UTC Unknown Mbps Unknown ms Unknown ms 2
Fail Oct 8, 2026 00:18 UTC Unknown Mbps Unknown ms Unknown ms 1
Fail Oct 8, 2026 00:17 UTC Unknown Mbps Unknown ms Unknown ms 1
OK Oct 7, 2026 01:17 UTC 0.2 Mbps 458 ms 4690 ms 0
Fail Oct 7, 2026 00:31 UTC Unknown Mbps Unknown ms Unknown ms 2
Fail Oct 7, 2026 00:16 UTC Unknown Mbps Unknown ms Unknown ms 1
Fail Oct 7, 2026 00:16 UTC Unknown Mbps Unknown ms Unknown ms 1
OK Oct 6, 2026 01:16 UTC 2.1 Mbps 362 ms 3670 ms 0
OK Oct 6, 2026 01:16 UTC Unknown Mbps Unknown ms Unknown ms 0
OK Oct 5, 2026 02:15 UTC Unknown Mbps 363 ms 3553 ms 0
OK Oct 5, 2026 02:15 UTC Unknown Mbps Unknown ms Unknown ms 0
OK Oct 4, 2026 03:15 UTC 0.7 Mbps 358 ms 3613 ms 0
Fail Oct 3, 2026 23:50 UTC Unknown Mbps Unknown ms Unknown ms 4
Fail Oct 3, 2026 22:23 UTC Unknown Mbps Unknown ms Unknown ms 3

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.

Live alternatives in South Korea

Fast global alternatives

Advertisement