节点已停止响应
此节点已无响应（经拨测确认）。推荐使用以下可用备选节点：
Netherlands (NL) — VLESS WS Node
Host: 46.243.142.2:443 • Tested: 8:55:14 AM
⚡ 浏览器端实时延迟测速
直接从您的当前浏览器向该节点发起真实 RTT 往返时延测算。
👍 Community Health Rating
Does this server currently connect and route traffic from your location?
🚀 一键导入客户端
直接点击下方按钮快速添加到主流代理软件：
📊 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 16:39:36 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 2a02:20b3:300:18::1 |
| Wed, 21 Oct 2026 16:04:20 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 2a02:20b3:300:18::1 |
| Wed, 21 Oct 2026 15:34:06 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 2a02:20b3:300:18::1 |
| Wed, 21 Oct 2026 15:03:53 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 2a02:20b3:300:18::1 |
| Wed, 21 Oct 2026 14:33:40 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 2a02:20b3:300:18::1 |
| Wed, 21 Oct 2026 13:58:35 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 2a02:20b3:300:18::1 |
| Wed, 21 Oct 2026 13:28:19 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 2a02:20b3:300:18::1 |
| Wed, 21 Oct 2026 12:57:51 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 2a02:20b3:300:18::1 |
| Wed, 21 Oct 2026 12:24:51 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 2a02:20b3:300:18::1 |
| Wed, 21 Oct 2026 11:52:11 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 2a02:20b3:300:18::1 |
| Wed, 21 Oct 2026 11:21:43 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 2a02:20b3:300:18::1 |
| Wed, 21 Oct 2026 11:20:40 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 2a02:20b3:300:18::1 |
| Wed, 21 Oct 2026 10:46:32 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 2a02:20b3:300:18::1 |
| Wed, 21 Oct 2026 10:10:47 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 2a02:20b3:300:18::1 |
| Wed, 21 Oct 2026 09:51:43 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 2a02:20b3:300:18::1 |
⚙️ 协议核心技术参数
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.
floweroom.vip): Utilizing discreet domain floweroom.vip enables the proxy tunnel to navigate Iranian and Chinese inspection hardware without triggering suspicion. ❓ Frequently Asked Questions for Node #17269974
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 floweroom.vip 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: 11🔓 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 | 6000 ms |
| Claude | ○ error | 🇩🇪 DE | request failed | — |
| TikTok | ○ error | — | request failed | — |
| Gemini | ● available | — | — | 2497 ms |
| NotebookLM | ○ error | — | request failed | — |
🤖 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 | ● reachable | 403 | answered, credentials not supplied | 2300 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)
🔄 客户端自动更新订阅
一键订阅所有 Netherlands 地区 VLESS 协议在线节点，支持后台自动同步：
✨ 同类可用节点推荐
同国家及同协议的高分备选可用节点：