Node No Longer Responding
This server is no longer responding (verified by our checker). Recommended working alternatives:
Germany (DE) — VLESS XHTTP Node
Host: 199.232.237.67:443 • Tested: 3:51:54 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 |
|---|---|---|---|---|
| Mon, 02 Nov 2026 04:12:05 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 483 ms | 2a01:4f8:c016:b9a5::1 |
| Mon, 02 Nov 2026 03:51:54 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 647 ms | 2a01:4f8:c016:b9a5::1 |
| Mon, 02 Nov 2026 03:45:04 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 2a01:4f8:c016:b9a5::1 |
| Mon, 02 Nov 2026 03:40:04 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 438 ms | 2a01:4f8:c016:b9a5::1 |
| Mon, 02 Nov 2026 03:34:44 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 2a01:4f8:c016:b9a5::1 |
| Mon, 02 Nov 2026 03:29:19 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 519 ms | 2a01:4f8:c016:b9a5::1 |
| Mon, 02 Nov 2026 03:24:11 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 493 ms | 2a01:4f8:c016:b9a5::1 |
| Mon, 02 Nov 2026 03:19:06 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 505 ms | 2a01:4f8:c016:b9a5::1 |
| Mon, 02 Nov 2026 03:13:58 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 607 ms | 2a01:4f8:c016:b9a5::1 |
| Mon, 02 Nov 2026 02:51:53 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 423 ms | 2a01:4f8:c016:b9a5::1 |
⚙️ 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
Node 199.232.***.***:443 runs on cutting-edge xHTTP transport, chunking data packets dynamically to foil GFW active probing sweeps.
ssl.fastly.com): Massive tech infrastructure domains like ssl.fastly.com are subjected to synthetic handshake replays by sophisticated inspection systems. ❓ Frequently Asked Questions for Node #23036232
How does node #N bypass state-level censorship and firewall restrictions? ▼
Node 199.232.***.***:443 runs on cutting-edge xHTTP transport, chunking data packets dynamically to foil GFW active probing sweeps. 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. Massive tech infrastructure domains like ssl.fastly.com are subjected to synthetic handshake replays by sophisticated inspection systems. 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: 26🔓 4. Service Availability & Anti-Bot Checks (Stash Checks)
| Service | Status | Region | Technical Detail | RTT |
|---|---|---|---|---|
| ChatGPT (web) | ● available | — | — | 707 ms |
| ChatGPT (app) | ● available | — | — | 560 ms |
| YouTube Premium | ● blocked | 🇮🇷 IR | not offered in this country | 615 ms |
| Netflix | ● available | 🇩🇪 DE | full catalogue | 1687 ms |
| Claude | ○ error | 🇩🇪 DE | Cloudflare challenged the request, so availability was never tested | 143 ms |
| TikTok | ● available | — | — | 907 ms |
| Gemini | ● blocked | 🇮🇷 IR | not offered in this country | 767 ms |
| NotebookLM | ● blocked | 🇮🇷 IR | not offered in this country | 1828 ms |
🤖 5. AI Model API Endpoints (Direct Probe)
| AI Endpoint | Vendor | State | HTTP | Detail | RTT |
|---|---|---|---|---|---|
| OpenAI | OpenAI | ● reachable | 401 | answered, credentials not supplied | 870 ms |
| Anthropic | Anthropic | ● reachable | 401 | answered, credentials not supplied | 682 ms |
| Google Gemini | ● reachable | 403 | answered, credentials not supplied | 530 ms | |
| DeepSeek | DeepSeek | ● reachable | 401 | answered, credentials not supplied | 779 ms |
| Qwen (Singapore) | Alibaba | ● reachable | 401 | answered, credentials not supplied | 1345 ms |
| Qwen (Beijing) | Alibaba | ● reachable | 401 | answered, credentials not supplied | 1267 ms |
| Kimi / Moonshot | Moonshot | ● reachable | 401 | answered, credentials not supplied | 1267 ms |
| Zhipu GLM | Zhipu | ● reachable | 401 | answered, credentials not supplied | 749 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 Germany VLESS nodes with automatic background updates:
✨ Related Working Nodes
Top verified alternatives with matching protocol and country: