Node No Longer Responding
This server is no longer responding (verified by our checker). Recommended working alternatives:
Germany (DE) — VLESS TCP Node
Host: static.122.183.105.178.clients.your-server.de:8443 • Tested: 1: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 02:51:53 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 2a01:4f8:1c1b:bb52::1 |
| Mon, 02 Nov 2026 02:47:15 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 2a01:4f8:1c1b:bb52::1 |
| Mon, 02 Nov 2026 02:42:06 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 2a01:4f8:1c1b:bb52::1 |
| Mon, 02 Nov 2026 02:37:02 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 2a01:4f8:1c1b:bb52::1 |
| Mon, 02 Nov 2026 02:31:10 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 573 ms | 2a01:4f8:1c1b:bb52::1 |
| Mon, 02 Nov 2026 02:25:12 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 573 ms | 2a01:4f8:1c1b:bb52::1 |
| Mon, 02 Nov 2026 02:20:09 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 528 ms | 2a01:4f8:1c1b:bb52::1 |
| Mon, 02 Nov 2026 02:15:08 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 563 ms | 2a01:4f8:1c1b:bb52::1 |
| Mon, 02 Nov 2026 02:10:01 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 566 ms | 2a01:4f8:1c1b:bb52::1 |
| Mon, 02 Nov 2026 02:04:55 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 689 ms | 2a01:4f8:1c1b:bb52::1 |
| Mon, 02 Nov 2026 01:59:09 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 601 ms | 2a01:4f8:1c1b:bb52::1 |
| Mon, 02 Nov 2026 01:53:59 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 657 ms | 2a01:4f8:1c1b:bb52::1 |
| Mon, 02 Nov 2026 01:51:54 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1006 ms | 2a01:4f8:1c1b:bb52::1 |
| Mon, 02 Nov 2026 01:48:46 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 582 ms | 2a01:4f8:1c1b:bb52::1 |
| Mon, 02 Nov 2026 01:43:34 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 526 ms | 2a01:4f8:1c1b:bb52::1 |
⚙️ Protocol Parameter Specification
Verified protocol configuration attributes required for manual client profiles.
Direct TLS Encrypted Channel (RAW / TCP)
Cryptographic resistance profile and Deep Packet Inspection (DPI) evasion analysis
Encrypted channel with clean TLS negotiation on host node-***.your-server.de, safeguarding packets from third-party interception and data tampering.
static.122.183.105.178.clients.your-server.de): Valid public key certificates bound directly to the server domain ensure unhindered transit across international corporate middleboxes. ❓ Frequently Asked Questions for Node #23007362
How does node #N bypass state-level censorship and firewall restrictions? ▼
Encrypted channel with clean TLS negotiation on host node-***.your-server.de, 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 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 8443 and domain masking perform under heavy censorship in Iran and China? ▼
Connections directed to port 8443 traverse middleboxes smoothly by mimicking auxiliary cloud service APIs. Valid public key certificates bound directly to the server domain ensure unhindered transit across international corporate middleboxes. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.
What steps should I take if node #N (node-***.your-server.de) 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: 25🔓 4. Service Availability & Anti-Bot Checks (Stash Checks)
| Service | Status | Region | Technical Detail | RTT |
|---|---|---|---|---|
| ChatGPT (web) | ● available | — | — | 1580 ms |
| ChatGPT (app) | ● available | — | — | 1397 ms |
| YouTube Premium | ● available | — | — | 1081 ms |
| Netflix | ● available | 🇩🇪 DE | full catalogue | 2517 ms |
| Claude | ○ error | 🇩🇪 DE | Cloudflare challenged the request, so availability was never tested | 475 ms |
| TikTok | ● available | — | — | 1178 ms |
| Gemini | ● available | — | — | 1088 ms |
| NotebookLM | ● available | — | sign-in required | 3575 ms |
🤖 5. AI Model API Endpoints (Direct Probe)
| AI Endpoint | Vendor | State | HTTP | Detail | RTT |
|---|---|---|---|---|---|
| OpenAI | OpenAI | ● reachable | 401 | answered, credentials not supplied | 1295 ms |
| Anthropic | Anthropic | ● reachable | 401 | answered, credentials not supplied | 1384 ms |
| Google Gemini | ● reachable | 403 | answered, credentials not supplied | 1209 ms | |
| DeepSeek | DeepSeek | ● reachable | 401 | answered, credentials not supplied | 1591 ms |
| Qwen (Singapore) | Alibaba | ● reachable | 401 | answered, credentials not supplied | 1610 ms |
| Qwen (Beijing) | Alibaba | ● reachable | 401 | answered, credentials not supplied | 1614 ms |
| Kimi / Moonshot | Moonshot | ● error | — | request failed | — |
| Zhipu GLM | Zhipu | ● reachable | 401 | answered, credentials not supplied | 1288 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: