Node No Longer Responding
This server is no longer responding (verified by our checker). Recommended working alternatives:
HK (HK) — VMESS WS Node
Host: 156.245.232.239:35043 • Tested: 12:51:43 PM
⚡ 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 |
|---|---|---|---|---|
| Wed, 21 Oct 2026 13:21:43 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 156.245.232.239 |
| Wed, 21 Oct 2026 12:51:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1810 ms | 156.245.232.239 |
| Wed, 21 Oct 2026 12:21:43 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 156.245.232.239 |
| Wed, 21 Oct 2026 11:51:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1265 ms | 156.245.232.239 |
| Wed, 21 Oct 2026 11:21:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 2700 ms | 156.245.232.239 |
| Wed, 21 Oct 2026 10:51:43 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 156.245.232.239 |
| Wed, 21 Oct 2026 10:21:43 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 156.245.232.239 |
| Wed, 21 Oct 2026 09:51:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1301 ms | 156.245.232.239 |
| Wed, 21 Oct 2026 09:13:40 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 2366 ms | 156.245.232.239 |
| Wed, 21 Oct 2026 08:55:14 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1981 ms | 156.245.232.239 |
| Wed, 21 Oct 2026 07:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 3061 ms | 156.245.232.239 |
| Wed, 21 Oct 2026 06:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 3038 ms | 156.245.232.239 |
| Wed, 21 Oct 2026 05:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1744 ms | 156.245.232.239 |
| Wed, 21 Oct 2026 05:25:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1450 ms | 156.245.232.239 |
| Wed, 21 Oct 2026 04:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 156.245.232.239 |
⚙️ Protocol Parameter Specification
Verified protocol configuration attributes required for manual client profiles.
Standard VMESS Proxy Relay
Cryptographic resistance profile and Deep Packet Inspection (DPI) evasion analysis
Standard VMESS proxy tunnel on server 156.245.***.***, optimal for transparent multi-region web acceleration.
❓ Frequently Asked Questions for Node #2877041
How does node #N bypass state-level censorship and firewall restrictions? ▼
Standard VMESS proxy tunnel on server 156.245.***.***, optimal for transparent multi-region web acceleration. 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 VMESS configuration? ▼
We advise using proven open-source clients supporting modern protocols: Happ, Clash Meta (Mihomo), Sing-box, v2rayNG, Streisand, and Hiddify. 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 35043 and domain masking perform under heavy censorship in Iran and China? ▼
Port 35043 is highly susceptible to automated firewall blacklisting due to anomalous socket behavior outside traditional web ports. Discreet masking evades detection. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.
What steps should I take if node #N (156.245.***.***) 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: 7🔓 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 | ○ error | — | request failed | — |
| Netflix | ○ error | — | request failed | 6068 ms |
| Claude | ○ error | 🇭🇰 HK | request failed | — |
| TikTok | ○ error | — | request failed | — |
| Gemini | ○ error | — | request failed | — |
| NotebookLM | ● blocked | — | not offered in this country | — |
🤖 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 | ● reachable | 401 | answered, credentials not supplied | 3787 ms |
| 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 VMESS nodes with automatic background updates:
✨ Related Working Nodes
Top verified alternatives with matching protocol and country: