Node No Longer Responding
This server is no longer responding (verified by our checker). Recommended working alternatives:
Netherlands (NL) — VLESS XHTTP Node
Host: 201.34.142.108:443 • Tested: 2:24:14 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, 04 Nov 2026 03:17:01 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 5.129.233.45 |
| Wed, 04 Nov 2026 03:06:02 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 5.129.233.45 |
| Wed, 04 Nov 2026 02:54:14 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 5.129.233.45 |
| Wed, 04 Nov 2026 02:50:00 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 5.129.233.45 |
| Wed, 04 Nov 2026 02:39:35 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 5.129.233.45 |
| Wed, 04 Nov 2026 02:28:01 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 5.129.233.45 |
| Wed, 04 Nov 2026 02:24:14 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 421 ms | 5.129.233.45 |
| Wed, 04 Nov 2026 02:16:56 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 5.129.233.45 |
| Wed, 04 Nov 2026 02:11:38 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 5.129.233.45 |
| Wed, 04 Nov 2026 01:55:23 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 5.129.233.45 |
| Wed, 04 Nov 2026 01:54:15 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 410 ms | 5.129.233.45 |
| Wed, 04 Nov 2026 01:50:22 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 5.129.233.45 |
| Wed, 04 Nov 2026 01:33:59 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 5.129.233.45 |
| Wed, 04 Nov 2026 01:12:34 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 5.129.233.45 |
| Wed, 04 Nov 2026 01:02:01 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 5.129.233.45 |
⚙️ 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
Engineered expressly to dismantle sovereign internet firewalls, xHTTP deployment on 201.34.***.***:443 delivers unbreakable packet egress.
201.34.142.108): Authentic hostname matching eliminates perimeter firewall suspicion by adhering strictly to standard HTTPS communication norms. ❓ Frequently Asked Questions for Node #23735560
How does node #N bypass state-level censorship and firewall restrictions? ▼
Engineered expressly to dismantle sovereign internet firewalls, xHTTP deployment on 201.34.***.***:443 delivers unbreakable packet egress. 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. Authentic hostname matching eliminates perimeter firewall suspicion by adhering strictly to standard HTTPS communication norms. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.
What steps should I take if node #N (201.34.***.***) 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: 24🔓 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 | ● blocked | 🇷🇺 RU | not offered in this country | 1759 ms |
| Netflix | ○ error | — | request failed | 6001 ms |
| Claude | ● available | 🇳🇱 NL | Anthropic API reachable | 433 ms |
| TikTok | ● available | — | — | 2231 ms |
| Gemini | ● blocked | 🇷🇺 RU | not offered in this country | 2131 ms |
| NotebookLM | ● blocked | 🇷🇺 RU | not offered in this country | 4050 ms |
🤖 5. AI Model API Endpoints (Direct Probe)
| AI Endpoint | Vendor | State | HTTP | Detail | RTT |
|---|---|---|---|---|---|
| OpenAI | OpenAI | ● error | — | request failed | — |
| Anthropic | Anthropic | ● reachable | 401 | answered, credentials not supplied | 1980 ms |
| Google Gemini | ● error | — | request failed | — | |
| DeepSeek | DeepSeek | ● error | — | request failed | — |
| Qwen (Singapore) | Alibaba | ● error | — | request failed | — |
| Qwen (Beijing) | Alibaba | ● reachable | 401 | answered, credentials not supplied | 2571 ms |
| Kimi / Moonshot | Moonshot | ● reachable | 401 | answered, credentials not supplied | 3099 ms |
| Zhipu GLM | Zhipu | ● reachable | 401 | answered, credentials not supplied | 2057 ms |
🗺️ 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: