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.142.25:443 • Tested: 5:12:04 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 |
|---|---|---|---|---|
| Sun, 25 Oct 2026 19:42:04 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 191.217.216.198 |
| Sun, 25 Oct 2026 19:15:20 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 191.217.216.198 |
| Sun, 25 Oct 2026 18:40:18 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 191.217.216.198 |
| Sun, 25 Oct 2026 18:12:04 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 191.217.216.198 |
| Sun, 25 Oct 2026 18:05:15 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 191.217.216.198 |
| Sun, 25 Oct 2026 17:30:14 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 191.217.216.198 |
| Sun, 25 Oct 2026 17:12:04 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1310 ms | 191.217.216.198 |
| Sun, 25 Oct 2026 17:10:09 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 3917 ms | 191.217.216.198 |
| Sun, 25 Oct 2026 16:30:06 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 5424 ms | 191.217.216.198 |
| Sun, 25 Oct 2026 16:12:04 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1614 ms | 191.217.216.198 |
| Sun, 25 Oct 2026 16:05:07 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 3810 ms | 191.217.216.198 |
| Sun, 25 Oct 2026 15:25:10 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 2069 ms | 191.217.216.198 |
| Sun, 25 Oct 2026 15:12:04 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1949 ms | 191.217.216.198 |
| Sun, 25 Oct 2026 14:50:03 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 2224 ms | 191.217.216.198 |
| Sun, 25 Oct 2026 14:40:08 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 4805 ms | 191.217.216.198 |
⚙️ 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.
slivdom-spb.site): Utilizing discreet domain slivdom-spb.site enables the proxy tunnel to navigate Iranian and Chinese inspection hardware without triggering suspicion. ❓ Frequently Asked Questions for Node #19260685
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. Utilizing discreet domain slivdom-spb.site enables the proxy tunnel to navigate Iranian and Chinese inspection hardware without triggering suspicion. 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: 20🔓 4. Service Availability & Anti-Bot Checks (Stash Checks)
| Service | Status | Region | Technical Detail | RTT |
|---|---|---|---|---|
| ChatGPT (web) | ● available | — | — | 2543 ms |
| ChatGPT (app) | ● available | — | — | 2818 ms |
| YouTube Premium | ● available | — | — | 3577 ms |
| Netflix | ● available | 🇳🇱 NL | full catalogue | 5987 ms |
| Claude | ○ error | 🇳🇱 NL | Cloudflare challenged the request, so availability was never tested | 2314 ms |
| TikTok | ● available | — | — | 4611 ms |
| Gemini | ● available | — | — | 3267 ms |
| NotebookLM | ● blocked | — | not offered in this country | — |
🤖 5. AI Model API Endpoints (Direct Probe)
| AI Endpoint | Vendor | State | HTTP | Detail | RTT |
|---|---|---|---|---|---|
| OpenAI | OpenAI | ● reachable | 401 | answered, credentials not supplied | 2946 ms |
| Anthropic | Anthropic | ● reachable | 401 | answered, credentials not supplied | 3055 ms |
| Google Gemini | ● reachable | 403 | answered, credentials not supplied | 2233 ms | |
| 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 Netherlands VLESS nodes with automatic background updates:
✨ Related Working Nodes
Top verified alternatives with matching protocol and country: