Node No Longer Responding
This server is no longer responding (verified by our checker). Recommended working alternatives:
Germany (DE) — VLESS WS Node
Host: 193.23.216.198:443 • Tested: 7:21:58 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, 03 Nov 2026 14:54:15 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 193.23.216.198 |
| Tue, 03 Nov 2026 11:24:14 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 193.23.216.198 |
| Tue, 03 Nov 2026 09:54:15 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 193.23.216.198 |
| Tue, 03 Nov 2026 08:42:58 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 193.23.216.198 |
| Tue, 03 Nov 2026 08:37:24 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 193.23.216.198 |
| Tue, 03 Nov 2026 08:24:15 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 193.23.216.198 |
| Tue, 03 Nov 2026 07:54:15 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 193.23.216.198 |
| Tue, 03 Nov 2026 07:24:14 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 193.23.216.198 |
| Tue, 03 Nov 2026 07:21:58 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 573 ms | 193.23.216.198 |
| Tue, 03 Nov 2026 07:17:05 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 546 ms | 193.23.216.198 |
| Tue, 03 Nov 2026 07:06:50 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 606 ms | 193.23.216.198 |
| Tue, 03 Nov 2026 06:50:02 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 564 ms | 193.23.216.198 |
| Tue, 03 Nov 2026 06:38:30 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 575 ms | 193.23.216.198 |
| Tue, 03 Nov 2026 06:27:41 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 557 ms | 193.23.216.198 |
| Tue, 03 Nov 2026 06:24:14 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1197 ms | 193.23.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
Server 193.23.***.***:443 deploys industry-standard TLS cryptographic protection across WS, ensuring complete confidentiality across Tier-1 International Carrier.
crt.onecloudstream.com): Masking under unobtrusive host crt.onecloudstream.com ensures outstanding longevity across mobile networks operated by MCI, Irancell, and Rightel. ❓ Frequently Asked Questions for Node #23418393
How does node #N bypass state-level censorship and firewall restrictions? ▼
Server 193.23.***.***:443 deploys industry-standard TLS cryptographic protection across WS, ensuring complete confidentiality across Tier-1 International Carrier. 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? ▼
Firewall gateways in Iran and China permit port 443 unconditionally to avoid breaking domestic banking portals and commercial digital services. Masking under unobtrusive host crt.onecloudstream.com ensures outstanding longevity across mobile networks operated by MCI, Irancell, and Rightel. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.
What steps should I take if node #N (193.23.***.***) 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: 23🔓 4. Service Availability & Anti-Bot Checks (Stash Checks)
| Service | Status | Region | Technical Detail | RTT |
|---|---|---|---|---|
| ChatGPT (web) | ● available | — | — | 1375 ms |
| ChatGPT (app) | ● available | — | — | 1181 ms |
| YouTube Premium | ● available | — | — | 1358 ms |
| Netflix | ● available | 🇩🇪 DE | full catalogue | 2300 ms |
| Claude | ● available | 🇩🇪 DE | Anthropic API reachable | 362 ms |
| TikTok | ● available | — | — | 1579 ms |
| Gemini | ● available | — | — | 1563 ms |
| NotebookLM | ● available | — | sign-in required | 2676 ms |
🤖 5. AI Model API Endpoints (Direct Probe)
| AI Endpoint | Vendor | State | HTTP | Detail | RTT |
|---|---|---|---|---|---|
| OpenAI | OpenAI | ● reachable | 401 | answered, credentials not supplied | 1477 ms |
| Anthropic | Anthropic | ● reachable | 401 | answered, credentials not supplied | 1280 ms |
| Google Gemini | ● reachable | 403 | answered, credentials not supplied | 1396 ms | |
| DeepSeek | DeepSeek | ● reachable | 401 | answered, credentials not supplied | 1591 ms |
| Qwen (Singapore) | Alibaba | ● reachable | 401 | answered, credentials not supplied | 1896 ms |
| Qwen (Beijing) | Alibaba | ● reachable | 401 | answered, credentials not supplied | 2273 ms |
| Kimi / Moonshot | Moonshot | ● reachable | 401 | answered, credentials not supplied | 2783 ms |
| Zhipu GLM | Zhipu | ● reachable | 401 | answered, credentials not supplied | 1366 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: