Node No Longer Responding
This server is no longer responding (verified by our checker). Recommended working alternatives:
Netherlands (NL) — VLESS WS Node
Host: 46.243.232.167:443 • Tested: 7: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 19:21:30 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 89.38.99.64 |
| Wed, 21 Oct 2026 18:48:50 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 89.38.99.64 |
| Wed, 21 Oct 2026 18:16:12 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 89.38.99.64 |
| Wed, 21 Oct 2026 17:42:53 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 89.38.99.64 |
| Wed, 21 Oct 2026 17:10:44 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 89.38.99.64 |
| Wed, 21 Oct 2026 16:39:36 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 89.38.99.64 |
| Wed, 21 Oct 2026 16:04:20 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 89.38.99.64 |
| Wed, 21 Oct 2026 15:34:06 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 89.38.99.64 |
| Wed, 21 Oct 2026 15:03:53 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 89.38.99.64 |
| Wed, 21 Oct 2026 14:33:40 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 89.38.99.64 |
| Wed, 21 Oct 2026 13:58:35 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 89.38.99.64 |
| Wed, 21 Oct 2026 13:28:19 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 89.38.99.64 |
| Wed, 21 Oct 2026 12:57:51 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 89.38.99.64 |
| Wed, 21 Oct 2026 12:24:51 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 89.38.99.64 |
| Wed, 21 Oct 2026 11:52:11 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 89.38.99.64 |
⚙️ 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
Protected by standard TLS encryption over WS, endpoint 46.243.***.***:443 guarantees private, uncompromised transit through international corridors.
uzs9w3bg6u.rucdncomp.pro): Perimeter firewalls flag and terminate external connections claiming domestic domain uzs9w3bg6u.rucdncomp.pro due to conflicting autonomous system paths. ❓ Frequently Asked Questions for Node #17446999
How does node #N bypass state-level censorship and firewall restrictions? ▼
Protected by standard TLS encryption over WS, endpoint 46.243.***.***: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? ▼
Traversing egress routes through port 443 provides maximum reliability since international border firewalls allow encrypted web handshakes unrestricted passage. Perimeter firewalls flag and terminate external connections claiming domestic domain uzs9w3bg6u.rucdncomp.pro due to conflicting autonomous system paths. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.
What steps should I take if node #N (46.243.***.***) 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: 27🔓 4. Service Availability & Anti-Bot Checks (Stash Checks)
| Service | Status | Region | Technical Detail | RTT |
|---|---|---|---|---|
| ChatGPT (web) | ● available | — | — | 3014 ms |
| ChatGPT (app) | ● available | — | — | 3199 ms |
| YouTube Premium | ● available | — | — | 3424 ms |
| Netflix | ● available | 🇳🇱 NL | full catalogue | 4907 ms |
| Claude | ○ error | 🇳🇱 NL | Cloudflare challenged the request, so availability was never tested | 752 ms |
| TikTok | ● available | — | — | 3523 ms |
| Gemini | ● available | — | — | 3411 ms |
| NotebookLM | ● available | — | sign-in required | 5722 ms |
🤖 5. AI Model API Endpoints (Direct Probe)
| AI Endpoint | Vendor | State | HTTP | Detail | RTT |
|---|---|---|---|---|---|
| OpenAI | OpenAI | ● reachable | 401 | answered, credentials not supplied | 3297 ms |
| Anthropic | Anthropic | ● reachable | 401 | answered, credentials not supplied | 3020 ms |
| Google Gemini | ● reachable | 403 | answered, credentials not supplied | 2949 ms | |
| DeepSeek | DeepSeek | ● reachable | 401 | answered, credentials not supplied | 3406 ms |
| Qwen (Singapore) | Alibaba | ● reachable | 401 | answered, credentials not supplied | 4036 ms |
| Qwen (Beijing) | Alibaba | ● error | — | request failed | — |
| Kimi / Moonshot | Moonshot | ● error | — | request failed | — |
| Zhipu GLM | Zhipu | ● reachable | 401 | answered, credentials not supplied | 3207 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: