Live Checked Japan OpenVPN server 219.100.37.221

Endpoint 219.100.37.221:443 / TCP 18Network scoreLow confidence · not a trust score

Download unavailable Report dead

🇯🇵 Japan Full-tunnel verified Recent Recent Source: AutoOVPN

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.

Limited or Stale server evidence

This endpoint remains available for reference, but it is marked noindex,follow and excluded from the stable-server sitemap until it has a current successful full-tunnel verification, an available configuration and real measurements.

Network score18/100Not a privacy or operator-trust score

Measured by PublicVPNList: throughput2.0 MbpsOct 8, 2026 22:19 UTC

Measured by PublicVPNList: tunnel RTT447 msmeasured

Reported by source: speedNot reported

Reported by source: pingNot reported

Protocol / portTCP 443

AvailabilityRecent

Successful checks shown8 / 20

Consecutive failed checks0 / 10

Last checked20 h ago

IP219.100.37.221

First seenOct 8, 2026

SourceAutoOVPN

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.221
proto	tcp
port	443
country	Japan
last checked	Oct 8, 2026 22:19 UTC
source	AutoOVPN

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 8, 2026 22:19 UTC, and the endpoint was first seen no later than Oct 8, 2026.

Check rows shown8 successful checks out of 20

Recent speedcurrent checker snapshot 2.0 Mbps

Recent latencycurrent checker snapshot 447 ms

Source provenanceAutoOVPN

Country speed comparisonFaster than 64%

Country latency rank#1126 of 1171

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 8, 2026 22:19 UTC

2.0Mbps 447Ping ms 4601TTT ms 0Failures

Fail

Oct 8, 2026 20:16 UTC

UnknownMbps UnknownPing ms UnknownTTT ms 5Failures

Fail

Oct 8, 2026 18:23 UTC

0.7Mbps 281Ping ms 3874TTT ms 4Failures

Fail

Oct 8, 2026 17:18 UTC

UnknownMbps UnknownPing ms UnknownTTT ms 3Failures

Fail

Oct 8, 2026 15:21 UTC

UnknownMbps UnknownPing ms UnknownTTT ms 2Failures

Fail

Oct 8, 2026 15:21 UTC

UnknownMbps UnknownPing ms UnknownTTT ms 1Failures

Fail

Oct 8, 2026 15:05 UTC

UnknownMbps UnknownPing ms UnknownTTT ms 1Failures

Fail

Oct 8, 2026 15:05 UTC