Node No Longer Responding
This server is no longer responding (verified by our checker). Recommended working alternatives:
Finland (FI) — VLESS WS Node
Host: 199.232.239.239:443 • Tested: 10:25: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 |
|---|---|---|---|---|
| Tue, 20 Oct 2026 23:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 65.109.211.46 |
| Tue, 20 Oct 2026 12:25:20 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 65.109.211.46 |
| Tue, 20 Oct 2026 11:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 65.109.211.46 |
| Tue, 20 Oct 2026 11:25:21 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 65.109.211.46 |
| Tue, 20 Oct 2026 10:25:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 2274 ms | 65.109.211.46 |
| Tue, 20 Oct 2026 09:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 65.109.211.46 |
| Tue, 20 Oct 2026 08:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 514 ms | 65.109.211.46 |
| Tue, 20 Oct 2026 07:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1431 ms | 157.180.83.47 |
| Tue, 20 Oct 2026 06:55:19 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 3539 ms | 2a01:4f9:c010:4e47::1 |
| Tue, 20 Oct 2026 05:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1278 ms | 65.109.211.46 |
| Tue, 20 Oct 2026 04:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 553 ms | 157.180.83.47 |
| Tue, 20 Oct 2026 03:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 866 ms | 65.109.176.67 |
| Tue, 20 Oct 2026 02:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 564 ms | 157.180.83.47 |
| Tue, 20 Oct 2026 01:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 594 ms | 65.109.211.46 |
| Tue, 20 Oct 2026 00:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 845 ms | 65.109.211.46 |
⚙️ 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
Encrypted channel with clean TLS negotiation on host 199.232.***.***, safeguarding packets from third-party interception and data tampering.
www.firefox.com): The Great Firewall actively replays TLS handshakes directed at www.firefox.com to identify and null-route unauthorized Reality endpoints. ❓ Frequently Asked Questions for Node #17133535
How does node #N bypass state-level censorship and firewall restrictions? ▼
Encrypted channel with clean TLS negotiation on host 199.232.***.***, safeguarding packets from third-party interception and data tampering. 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? ▼
Operating over standard port 443 bypasses common heuristic firewall rules that automatically discard anomalous transport layer assignments. The Great Firewall actively replays TLS handshakes directed at www.firefox.com to identify and null-route unauthorized Reality endpoints. 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: 11🔓 4. Service Availability & Anti-Bot Checks (Stash Checks)
| Service | Status | Region | Technical Detail | RTT |
|---|---|---|---|---|
| ChatGPT (web) | ● available | — | — | 2588 ms |
| ChatGPT (app) | ○ error | — | request failed | — |
| YouTube Premium | ○ error | — | request failed | — |
| Netflix | ○ error | — | request failed | 6007 ms |
| Claude | ○ error | 🇫🇮 FI | request failed | — |
| TikTok | ○ error | — | request failed | — |
| 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 | 2335 ms |
| Anthropic | Anthropic | ● reachable | 401 | answered, credentials not supplied | 2371 ms |
| Google Gemini | ● reachable | 403 | answered, credentials not supplied | 2871 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 Finland VLESS nodes with automatic background updates:
✨ Related Working Nodes
Top verified alternatives with matching protocol and country: