Node No Longer Responding
This server is no longer responding (verified by our checker). Recommended working alternatives:
Netherlands (NL) — VLESS XHTTP Node
Host: 199.232.78.160:443 • Tested: 11:55:20 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 |
|---|---|---|---|---|
| Wed, 21 Oct 2026 09:13:40 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 144.124.240.30 |
| Wed, 21 Oct 2026 07:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 144.124.240.30 |
| Tue, 20 Oct 2026 15:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 144.124.240.30 |
| Tue, 20 Oct 2026 15:25:20 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 144.124.240.30 |
| Tue, 20 Oct 2026 14:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 144.124.240.30 |
| Tue, 20 Oct 2026 14:25:20 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 144.124.240.30 |
| Tue, 20 Oct 2026 13:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 144.124.240.30 |
| Tue, 20 Oct 2026 13:25:20 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 144.124.240.30 |
| Tue, 20 Oct 2026 12:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 144.124.240.30 |
| Tue, 20 Oct 2026 11:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1170 ms | 144.124.240.30 |
| Tue, 20 Oct 2026 11:25:21 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 144.124.240.30 |
| Tue, 20 Oct 2026 10:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 144.124.240.30 |
| Tue, 20 Oct 2026 09:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1823 ms | 144.124.240.30 |
⚙️ Protocol Parameter Specification
Verified protocol configuration attributes required for manual client profiles.
Asynchronous xHTTP Split-Stream Mesh
Cryptographic resistance profile and Deep Packet Inspection (DPI) evasion analysis
Advanced xHTTP protocol architecture on 199.232.***.*** breaks data streams into irregular segments, defeating entropy-based filtering appliances.
www.firefox.com): Censorship filters in China and Iran cross-reference SNI www.firefox.com against authentic regional IP clusters, terminating unverified routing pairs. ❓ Frequently Asked Questions for Node #17318527
How does node #N bypass state-level censorship and firewall restrictions? ▼
Advanced xHTTP protocol architecture on 199.232.***.*** breaks data streams into irregular segments, defeating entropy-based filtering appliances. 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 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 443 and domain masking perform under heavy censorship in Iran and China? ▼
Selecting port 443 allows client connections to blend seamlessly with millions of simultaneous browser sessions across international border checkpoints. Censorship filters in China and Iran cross-reference SNI www.firefox.com against authentic regional IP clusters, terminating unverified routing pairs. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.
What steps should I take if node #N (199.232.***.***) 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: 17🔓 4. Service Availability & Anti-Bot Checks (Stash Checks)
| Service | Status | Region | Technical Detail | RTT |
|---|---|---|---|---|
| ChatGPT (web) | ● available | — | — | 1165 ms |
| ChatGPT (app) | ○ error | — | request failed | — |
| YouTube Premium | ● available | — | — | 2641 ms |
| Netflix | ● available | 🇳🇱 NL | full catalogue | 2277 ms |
| Claude | ○ error | 🇳🇱 NL | Cloudflare challenged the request, so availability was never tested | 1194 ms |
| TikTok | ● available | — | — | 1382 ms |
| Gemini | ○ error | — | request failed | — |
| NotebookLM | ○ error | — | request failed | — |
🤖 5. AI Model API Endpoints (Direct Probe)
| AI Endpoint | Vendor | State | HTTP | Detail | RTT |
|---|---|---|---|---|---|
| OpenAI | OpenAI | ● reachable | 401 | answered, credentials not supplied | 1567 ms |
| Anthropic | Anthropic | ● reachable | 401 | answered, credentials not supplied | 820 ms |
| Google Gemini | ● error | — | request failed | — | |
| DeepSeek | DeepSeek | ● error | — | request failed | — |
| Qwen (Singapore) | Alibaba | ● reachable | 401 | answered, credentials not supplied | 1180 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 Netherlands VLESS nodes with automatic background updates:
✨ Related Working Nodes
Top verified alternatives with matching protocol and country: