Live Checked Japan OpenVPN server 219.100.37.61

Endpoint 219.100.37.61:443 / TCP 33Network scoreLow confidence · not a trust score

Report dead

🇯🇵 Japan Full-tunnel verified Fresh Fresh Source: IPSpeed

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 score33/100Not a privacy or operator-trust score

Measured by PublicVPNList: throughput1.2 MbpsOct 14, 2026 21:27 UTC

Measured by PublicVPNList: tunnel RTT283 msopenvpn_tunnel_recovery_v1

Reported by source: speedNot reported

Reported by source: pingNot reported

Protocol / portTCP 443

AvailabilityFresh

Successful checks shown11 / 20

Consecutive failed checks0 / 10

Last checked36 min ago

IP219.100.37.61

First seenOct 14, 2026

SourceIPSpeed

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	219.100.37.61
proto	tcp
port	443
country	Japan
last checked	Oct 14, 2026 21:27 UTC
source	IPSpeed

Safety note

TCP 443 safety note

TCP 443 can be useful on restrictive networks, but it is not a privacy guarantee and it is not invisible. Treat it as a connectivity option, not as proof that the VPN operator is trustworthy. Compare freshness, latency and score before downloading, then verify IP and DNS after connecting.

Server evidence summary

This detail page is built from the current published snapshot. The latest successful check for this endpoint is Oct 14, 2026 21:27 UTC, and the endpoint was first seen no later than Oct 14, 2026.

Check rows shown11 successful checks out of 20

Recent speedcurrent checker snapshot 1.2 Mbps

Recent latencycurrent checker snapshot 283 ms

Source provenanceIPSpeed

Country speed comparisonFaster than 47%

Country latency rank#82 of 1152

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.

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.

Latency history

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

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.

Oct 14, 2026 21:27 UTC

1.2Mbps 283Ping ms 5713TTT ms 0Failures

Fail

Oct 14, 2026 19:49 UTC

UnknownMbps UnknownPing ms UnknownTTT ms 3Failures

Fail

Oct 14, 2026 19:04 UTC

UnknownMbps UnknownPing ms UnknownTTT ms 2Failures

Fail

Oct 14, 2026 18:49 UTC

UnknownMbps UnknownPing ms UnknownTTT ms 1Failures

Oct 14, 2026 18:48 UTC

2.4Mbps 368Ping ms 4183TTT ms 0Failures

Oct 13, 2026 19:47 UTC

2.4Mbps 282Ping ms 3921TTT ms 0Failures

Oct 13, 2026 19:46 UTC