Node No Longer Responding
This server is no longer responding (verified by our checker). Recommended working alternatives:
HK (HK) — VLESS WS Node
Host: 172.67.149.199:443 • Tested: 2:23:15 AM
⚡ 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:
📊 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 |
|---|---|---|---|---|
| Tue, 03 Nov 2026 02:24:14 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 47.79.19.147 |
| Tue, 03 Nov 2026 02:23:15 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 1419 ms | 47.79.19.147 |
| Tue, 03 Nov 2026 02:08:05 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 47.79.19.147 |
| Tue, 03 Nov 2026 02:03:06 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 5753 ms | 47.79.19.147 |
| Tue, 03 Nov 2026 01:58:12 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 4393 ms | 47.79.19.147 |
| Tue, 03 Nov 2026 01:53:06 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 1970 ms | 47.79.19.147 |
| Tue, 03 Nov 2026 01:43:09 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 5703 ms | 47.79.19.147 |
| Tue, 03 Nov 2026 01:38:01 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 5717 ms | 47.79.19.147 |
| Tue, 03 Nov 2026 01:33:04 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 3087 ms | 47.79.19.147 |
| Tue, 03 Nov 2026 01:24:15 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 2241 ms | 47.79.19.147 |
| Tue, 03 Nov 2026 01:17:03 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 3706 ms | 47.79.19.147 |
| Tue, 03 Nov 2026 00:55:59 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 47.79.19.147 |
| Tue, 03 Nov 2026 00:50:01 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 3415 ms | 47.79.19.147 |
| Tue, 03 Nov 2026 00:44:54 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 4774 ms | 47.79.19.147 |
| Tue, 03 Nov 2026 00:44:16 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 2493 ms | 47.79.19.147 |
⚙️ Protocol Parameter Specification
Verified protocol configuration attributes required for manual client profiles.
Direct TLS Encrypted Channel (WS)
Cryptographic resistance profile and Deep Packet Inspection (DPI) evasion analysis
Standard TLS deployment over WS on server 172.67.***.*** delivers dependable international throughput with an uptime rating of 99.6%.
px2.5ibtc.cn): Spoofing sovereign regional service px2.5ibtc.cn constitutes an operational flaw that causes immediate connection termination. ❓ Frequently Asked Questions for Node #22521891
How does node #N bypass state-level censorship and firewall restrictions? ▼
Standard TLS deployment over WS on server 172.67.***.*** delivers dependable international throughput with an uptime rating of 99.6%. 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? ▼
Using port 443 minimizes transit packet loss and prevents artificial connection resetting on congested undersea fiber cables. Spoofing sovereign regional service px2.5ibtc.cn constitutes an operational flaw that causes immediate connection termination. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.
What steps should I take if node #N (172.67.***.***) 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: 12🔓 4. Service Availability & Anti-Bot Checks (Stash Checks)
| Service | Status | Region | Technical Detail | RTT |
|---|---|---|---|---|
| ChatGPT (web) | ○ error | — | request failed | — |
| ChatGPT (app) | ● blocked | — | blocked | 5200 ms |
| YouTube Premium | ○ error | — | request failed | — |
| Netflix | ○ error | — | request failed | 6092 ms |
| Claude | ○ error | 🇭🇰 HK | 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)
🔄 Auto-Updating App Subscriptions
Subscribe to all active verified HK VLESS nodes with automatic background updates:
✨ Related Working Nodes
Top verified alternatives with matching protocol and country: