Node No Longer Responding
This server is no longer responding (verified by our checker). Recommended working alternatives:
Germany (DE) — VMESS TCP Node
Host: 5.45.97.147:10803 • Tested: 5:25:20 PM
⚡ 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 |
|---|---|---|---|---|
| Wed, 21 Oct 2026 06:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 5.45.97.147 |
| Wed, 21 Oct 2026 06:25:21 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 5.45.97.147 |
| Wed, 21 Oct 2026 05:25:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 5.45.97.147 |
| Wed, 21 Oct 2026 04:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 5.45.97.147 |
| Wed, 21 Oct 2026 04:25:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 5.45.97.147 |
| Wed, 21 Oct 2026 03:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 5.45.97.147 |
| Tue, 20 Oct 2026 22:25:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 5.45.97.147 |
| Tue, 20 Oct 2026 21:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 5.45.97.147 |
| Tue, 20 Oct 2026 21:25:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 5.45.97.147 |
| Tue, 20 Oct 2026 20:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 5.45.97.147 |
| Tue, 20 Oct 2026 20:25:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 5.45.97.147 |
| Tue, 20 Oct 2026 19:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 5.45.97.147 |
| Tue, 20 Oct 2026 19:25:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 5.45.97.147 |
| Tue, 20 Oct 2026 18:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 5.45.97.147 |
| Tue, 20 Oct 2026 18:25:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 5.45.97.147 |
⚙️ Protocol Parameter Specification
Verified protocol configuration attributes required for manual client profiles.
Standard VMESS Proxy Relay
Cryptographic resistance profile and Deep Packet Inspection (DPI) evasion analysis
Unadorned VMESS relay running on port 10803 with an empirical response latency of 58 ms.
❓ Frequently Asked Questions for Node #42034
How does node #N bypass state-level censorship and firewall restrictions? ▼
Unadorned VMESS relay running on port 10803 with an empirical response latency of 58 ms. 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 VMESS 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 10803 and domain masking perform under heavy censorship in Iran and China? ▼
Using port 10803 introduces substantial connection instability when operating under strict government-mandated firewall lockdowns. Discreet masking evades detection. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.
What steps should I take if node #N (5.45.***.***) 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 | — | — | 1817 ms |
| ChatGPT (app) | ● available | — | — | 1671 ms |
| YouTube Premium | ● available | — | — | 2009 ms |
| Netflix | ● available | 🇩🇪 DE | full catalogue | 5226 ms |
| Claude | ○ error | 🇩🇪 DE | Cloudflare challenged the request, so availability was never tested | 188 ms |
| TikTok | ● available | — | — | 2007 ms |
| Gemini | ○ error | — | request failed | — |
| NotebookLM | ● available | — | sign-in required | 2888 ms |
🤖 5. AI Model API Endpoints (Direct Probe)
| AI Endpoint | Vendor | State | HTTP | Detail | RTT |
|---|---|---|---|---|---|
| OpenAI | OpenAI | ● reachable | 401 | answered, credentials not supplied | 1903 ms |
| Anthropic | Anthropic | ● reachable | 401 | answered, credentials not supplied | 2073 ms |
| Google Gemini | ● reachable | 403 | answered, credentials not supplied | 1911 ms | |
| DeepSeek | DeepSeek | ● reachable | 401 | answered, credentials not supplied | 1594 ms |
| Qwen (Singapore) | Alibaba | ● reachable | 401 | answered, credentials not supplied | 2173 ms |
| Qwen (Beijing) | Alibaba | ● error | — | request failed | — |
| Kimi / Moonshot | Moonshot | ● error | — | request failed | — |
| Zhipu GLM | Zhipu | ● reachable | 401 | answered, credentials not supplied | 1695 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 VMESS nodes with automatic background updates:
✨ Related Working Nodes
Top verified alternatives with matching protocol and country: