🌐 VLESS REALITY Live Verified Node

HK (HK) — VLESS TCP Node

Host: 165.154.63.139:443 • Tested: 4:24:15 AM

Checked Latency 994 ms

Est. Bandwidth 0.0 Mbps

24h Uptime SLA 100%

Exit Consensus HK (Verified)

⚡ Direct Connection URI (VLESS • HK) Xray-core Verified • 100% Uptime

vless://91ad30e9-ab06-4b4c-9fb9-1c2aa97d8b3a@165.154.63.139:443?flow=xtls-rprx-vision&fp=chrome&path=%2F&pbk=AE81BrwMc8-kwGEIA1LhzaL03er0Qwt2V-fFy76F5jQ&security=reality&sid=ca4aedd4&sni=www.amazon.com&type=tcp#%F0%9F%8C%90HK-freevpnkeys.com-TG-%40yavpn_robot

1. Direct Single Key Copy the URI above into Happ, Incy, v2RayTun, or v2rayNG. Re-tested every 30 min.

2. Free Auto-Updating Subscription Auto-sync fresh working nodes every 30 min: https://freevpnkeys.com/sub/happ

3. Private 10 Gbps Anti-DPI Multi-Key Need zero congestion, 10 Gbps speed & strict ISP whitelist bypass? Get a private key in Telegram bot @yavpn_robot (~$0.05/day).

⚡ Interactive Browser Ping Test

Direct client-to-node round-trip time (RTT) measured in your browser.

👍 Community Health Rating

Does this server currently connect and route traffic from your location?

🚀 1-Click App Import

Instantly add this proxy node to your favorite client application:

Happ ↗

iOS / Android / PC / Mac

v2RayTun ↗

Android / iOS / PC / Mac

Incy ↗

iOS / Android / PC / Mac

v2rayNG ↗

Android

FlClashX / Clash ↗

Windows / macOS / Android

Karing / sing-box ↗

Core / GUI

📊 Recent Verification History

Automated multi-point health probes through Xray-core / libxray (verified every 30 minutes)

24h SLA: 100% (24 probes)

Probe Time	Probe Node	Verdict	Latency (RTT)	Exit IP
Wed, 04 Nov 2026 04:24:15 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	994 ms	165.154.63.139
Wed, 04 Nov 2026 03:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	886 ms	165.154.63.139
Wed, 04 Nov 2026 02:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1135 ms	165.154.63.139
Wed, 04 Nov 2026 01:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	947 ms	165.154.63.139
Wed, 04 Nov 2026 00:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	603 ms	165.154.63.139
Tue, 03 Nov 2026 23:24:15 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1049 ms	165.154.63.139
Tue, 03 Nov 2026 22:24:15 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	750 ms	165.154.63.139
Tue, 03 Nov 2026 21:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	562 ms	165.154.63.139
Tue, 03 Nov 2026 20:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1053 ms	165.154.63.139
Tue, 03 Nov 2026 19:24:15 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	852 ms	165.154.63.139
Tue, 03 Nov 2026 18:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	915 ms	165.154.63.139
Tue, 03 Nov 2026 17:24:15 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	2105 ms	165.154.63.139
Tue, 03 Nov 2026 16:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1007 ms	165.154.63.139
Tue, 03 Nov 2026 15:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1104 ms	165.154.63.139
Tue, 03 Nov 2026 14:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	632 ms	165.154.63.139

⚙️ Protocol Parameter Specification

Verified protocol configuration attributes required for manual client profiles.

Host / Address 165.154.63.139

Port 443

Security Protocol REALITY

Transport Type TCP

SNI (Server Name Indication) www.amazon.com

Public Key (pbk) AE81BrwMc8-kwGEIA1LhzaL03er0Qwt2V-fFy76F5jQ

Short ID (sid) ca4aedd4

Flow xtls-rprx-vision

Path /

UUID 91ad30e9-ab06-4b4c-9fb9-1c2aa97d8b3a

TLS Fingerprint 20638059

🛡️

Zero-Signature Reality Relay (RAW / TCP)

Cryptographic resistance profile and Deep Packet Inspection (DPI) evasion analysis

SNI: Major Cloud Target SNI (Active Probe Susceptibility) Port 443 (Universal HTTPS Gateway) uTLS: 20638059 Custom Handshake (Active Cloaking)

Featuring high-throughput RAW / TCP connectivity on host 165.154.***.***, the server operates with zero identifiable metadata fingerprints across international borders.

Network Port Analysis: Firewall gateways in Iran and China permit port 443 unconditionally to avoid breaking domestic banking portals and commercial digital services.

SNI Masking Analysis (www.amazon.com): Employing prominent hostname www.amazon.com elevates detection probability because national firewalls closely monitor inbound cloud traffic distributions.

uTLS Handshake Security Analysis (20638059): Emulating 20638059 safeguards the encrypted stream from unauthorized fingerprint correlation across public internet exchanges.

Flow Technology: Vision padding ("xtls-rprx-vision") randomizes encrypted payload lengths, preventing DPI middleboxes from measuring TLS negotiation characteristics.

Client Handshake Masking (uTLS): Emulating 20638059 safeguards the encrypted stream from unauthorized fingerprint correlation across public internet exchanges.

REALITY Cryptography: Reality encryption utilizing token (ca4aedd4) ensures complete forward secrecy and eliminates proxy detection risks.

❓ Frequently Asked Questions for Node #20638059

How does node #N bypass state-level censorship and firewall restrictions? ▼

Featuring high-throughput RAW / TCP connectivity on host 165.154.***.***, the server operates with zero identifiable metadata fingerprints across international borders. Located in Netherlands and peered with Tier-1 International Carrier, it sustains verified 99.6% reliability with low response times around 58 ms.

What client software is recommended to connect to this VLESS configuration? ▼

We advise using proven clients supporting modern protocols: Happ, Incy (incy.cc), v2RayTun, Clash Meta (Mihomo), Sing-box, v2rayNG, and Streisand. Each platform supports direct QR scanning and instant URI import.

Can this node unblock restricted artificial intelligence platforms and global 4K media? ▼

Yes. Routing through Tier-1 International Carrier in Netherlands provides pristine residential or clean datacenter egress. Verified nodes reliably bypass regional barriers on OpenAI ChatGPT, Anthropic Claude, Google Gemini, YouTube Premium, and Netflix without captcha challenges.

How do port 443 and domain masking perform under heavy censorship in Iran and China? ▼

Firewall gateways in Iran and China permit port 443 unconditionally to avoid breaking domestic banking portals and commercial digital services. Employing prominent hostname www.amazon.com elevates detection probability because national firewalls closely monitor inbound cloud traffic distributions. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.

What steps should I take if node #N (165.154.***.***) experiences a connection timeout? ▼

Our automated probing infrastructure validates public keys continuously. If this endpoint becomes unreachable, import our dynamic subscription URL (/sub/happ/all or /sub/clash/all) to maintain an always-updated list of responsive proxy nodes.

🌐 7-Service Geocheck & Regional Consensus

Authentic multi-provider exit node audit across 16 GeoIP databases, RIPE/ASN, proxycheck.io v3, CDN PoP, AI APIs, and Stash probes.

GeoCheck v1.4 ⏱ 12.36s

1. Exit IP & Autonomous System (Identity) 🇭🇰 HK

Public Exit IPv4: 165.154.63.139

Network (ASN / Org): AS135377 · UCLOUD INFORMATION TECHNOLOGY (HK) LIMITED

BGP Prefix / Subnet: —

Node Location: Hong Kong — 🇭🇰 HK

2. IP Address Reputation (proxycheck.io v3) Hosting

Address Class: 🖥️ Hosting / Datacenter

Risk Score:

20 / 100 (95% conf)

Detection Flags:

hosting

Operator / Provider: UCLOUD INFORMATION TECHNOLOGY (HK) LIMITED

3. Geolocation Consensus (IPv4)

Providers tallied: 24

🇭🇰 HK Hong Kong

100% (24/24)

🔓 4. Service Availability & Anti-Bot Checks (Stash Checks)

Service	Status	Region	Technical Detail	RTT
ChatGPT (web)	● blocked	—	the API refused this region	2230 ms
ChatGPT (app)	● blocked	—	the API refused this region	2126 ms
YouTube Premium	● available	—	—	2123 ms
Netflix	○ error	—	request failed	4419 ms
Claude	● blocked	🇭🇰 HK	the API refused this region	3304 ms
TikTok	○ error	—	request failed	—
Gemini	● available	—	—	2514 ms
NotebookLM	● blocked	—	not offered in this country	—

🤖 5. AI Model API Endpoints (Direct Probe)

AI Endpoint	Vendor	State	HTTP	Detail	RTT
OpenAI	OpenAI	● blocked	403	the API refused this region	2605 ms
Anthropic	Anthropic	● blocked	403	the API refused this region	2305 ms
Google Gemini	Google	● reachable	403	answered, credentials not supplied	2315 ms
DeepSeek	DeepSeek	● reachable	401	answered, credentials not supplied	2128 ms
Qwen (Singapore)	Alibaba	● reachable	401	answered, credentials not supplied	2503 ms
Qwen (Beijing)	Alibaba	● error	—	request failed	—
Kimi / Moonshot	Moonshot	● error	—	request failed	—
Zhipu GLM	Zhipu	● reachable	401	answered, credentials not supplied	2312 ms