HK (HK) — VLESS WS Node
Host: 83.229.123.135:443 • Tested: 4:07:46 PM
vless://495c7195-85b8-498a-bf20-2ea9ce9175b5@83.229.123.135:443?&security=tls&fp=chrome&sni=snip.edgeoneai.cc.cd&type=ws&headerType=none&host=snip.edgeoneai.cc.cd&path=%2Ffdip%3Dsstp%3A%2F%2Fvpn%3Avpn%40public-vpn-200.opengw.net%3A443%3Fed%3D2560fp%3Dchromefp%3Dchrome#%F0%9F%8C%90HK-freevpnkeys.com-TG-%40yavpn_robot https://freevpnkeys.com/sub/happ ⚡ 浏览器端实时延迟测速
直接从您的当前浏览器向该节点发起真实 RTT 往返时延测算。
👍 Community Health Rating
Does this server currently connect and route traffic from your location?
🚀 一键导入客户端
直接点击下方按钮快速添加到主流代理软件：
📊 Recent Verification History
Automated multi-point health probes through Xray-core / libxray (verified every 30 minutes)
| Probe Time | Probe Node | Verdict | Latency (RTT) | Exit IP |
|---|---|---|---|---|
| Wed, 21 Oct 2026 16:07:46 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1404 ms | 2a09:bac5:3989:2e1e::498:33 |
| Wed, 21 Oct 2026 15:21:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 746 ms | 2a09:bac5:3989:263c::3cf:3a |
| Wed, 21 Oct 2026 14:21:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 748 ms | 2a09:bac5:3989:16d2::246:c6 |
| Wed, 21 Oct 2026 13:21:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 2650 ms | 2a09:bac5:3989:e6::17:36d |
| Wed, 21 Oct 2026 12:21:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 950 ms | 2a09:bac5:3989:e6::17:36d |
| Wed, 21 Oct 2026 11:51:43 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 2a09:bac5:3989:2e1e::498:33 |
| Wed, 21 Oct 2026 11:21:43 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 2a09:bac5:3989:2e1e::498:33 |
| Wed, 21 Oct 2026 10:21:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 589 ms | 2a09:bac5:3989:16d2::246:bc |
| Wed, 21 Oct 2026 09:51:43 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 2a09:bac5:3989:2e1e::498:33 |
| Wed, 21 Oct 2026 08:55:14 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 564 ms | 2a09:bac5:3989:e6::17:338 |
| Wed, 21 Oct 2026 07:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1142 ms | 2a09:bac5:3989:e6::17:373 |
⚙️ 协议核心技术参数
Verified protocol configuration attributes required for manual client profiles.
Direct TLS Encrypted Channel (WS)
Cryptographic resistance profile and Deep Packet Inspection (DPI) evasion analysis
Protected by standard TLS encryption over WS, endpoint 83.229.***.***:443 guarantees private, uncompromised transit through international corridors.
snip.edgeoneai.cc.cd): Camouflaged behind neutral destination snip.edgeoneai.cc.cd, this node avoids heuristic scrutiny and active probe lists maintained by authoritarian firewalls. ❓ Frequently Asked Questions for Node #17717274
How does node #N bypass state-level censorship and firewall restrictions? ▼
Protected by standard TLS encryption over WS, endpoint 83.229.***.***:443 guarantees private, uncompromised transit through international corridors. 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? ▼
Port 443 functions as the bedrock gateway for encrypted web communications, making discriminatory packet drops virtually impossible without crippling nationwide commerce. Camouflaged behind neutral destination snip.edgeoneai.cc.cd, this node avoids heuristic scrutiny and active probe lists maintained by authoritarian firewalls. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.
What steps should I take if node #N (83.229.***.***) 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.
3. Geolocation Consensus (IPv4)
Providers tallied: 6🔓 4. Service Availability & Anti-Bot Checks (Stash Checks)
| Service | Status | Region | Technical Detail | RTT |
|---|---|---|---|---|
| ChatGPT (web) | ○ error | — | request failed | — |
| ChatGPT (app) | ○ error | — | request failed | — |
| YouTube Premium | ● available | — | — | 5097 ms |
| Netflix | ○ error | — | request failed | 6087 ms |
| Claude | ○ error | — | request failed | — |
| TikTok | ○ error | — | request failed | — |
| Gemini | ○ error | — | request failed | — |
| NotebookLM | ○ error | — | request failed | — |
🤖 5. AI Model API Endpoints (Direct Probe)
| AI Endpoint | Vendor | State | HTTP | Detail | RTT |
|---|---|---|---|---|---|
| OpenAI | OpenAI | ● error | — | request failed | — |
| Anthropic | Anthropic | ● error | — | request failed | — |
| Google Gemini | ● error | — | request failed | — | |
| DeepSeek | DeepSeek | ● error | — | request failed | — |
| Qwen (Singapore) | Alibaba | ● error | — | request failed | — |
| Qwen (Beijing) | Alibaba | ● error | — | request failed | — |
| Kimi / Moonshot | Moonshot | ● error | — | request failed | — |
| Zhipu GLM | Zhipu | ● error | — | request failed | — |
🗺️ 6. GeoIP Databases (16 Independent Providers)
7. Popular Services Geo Detection (21 probes)
8. CDN Edge Location (PoP)
🔄 客户端自动更新订阅
一键订阅所有 HK 地区 VLESS 协议在线节点，支持后台自动同步：
✨ 同类可用节点推荐
同国家及同协议的高分备选可用节点：