Node No Longer Responding
This server is no longer responding (verified by our checker). Recommended working alternatives:
Germany (DE) — VLESS TCP Node
Host: 150.241.101.80:8443 • Tested: 12:21:43 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 14:21:43 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 150.241.101.80 |
| Wed, 21 Oct 2026 13:51:43 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 150.241.101.80 |
| Wed, 21 Oct 2026 13:21:43 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 150.241.101.80 |
| Wed, 21 Oct 2026 12:21:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1187 ms | 150.241.101.80 |
| Wed, 21 Oct 2026 11:51:43 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 150.241.101.80 |
| Wed, 21 Oct 2026 10:51:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 738 ms | 150.241.101.80 |
| Wed, 21 Oct 2026 09:51:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1340 ms | 150.241.101.80 |
| Wed, 21 Oct 2026 08:55:14 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1420 ms | 150.241.101.80 |
| Wed, 21 Oct 2026 07:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 2051 ms | 150.241.101.80 |
| Wed, 21 Oct 2026 06:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 2198 ms | 150.241.101.80 |
| Wed, 21 Oct 2026 05:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 905 ms | 150.241.101.80 |
| Wed, 21 Oct 2026 04:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 740 ms | 150.241.101.80 |
| Wed, 21 Oct 2026 03:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1044 ms | 150.241.101.80 |
| Wed, 21 Oct 2026 02:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 310 ms | 150.241.101.80 |
| Wed, 21 Oct 2026 01:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 909 ms | 150.241.101.80 |
⚙️ Protocol Parameter Specification
Verified protocol configuration attributes required for manual client profiles.
Perimeter-Defeating VLESS Node
Cryptographic resistance profile and Deep Packet Inspection (DPI) evasion analysis
Node 150.241.***.*** routes encrypted packets across Tier-1 International Carrier via RAW / TCP, delivering robust anti-censorship resistance for users on restricted cellular carriers like MCI and Irancell.
yandex.net): Spoofing sovereign regional service yandex.net constitutes an operational flaw that causes immediate connection termination. ❓ Frequently Asked Questions for Node #13777764
How does node #N bypass state-level censorship and firewall restrictions? ▼
Node 150.241.***.*** routes encrypted packets across Tier-1 International Carrier via RAW / TCP, delivering robust anti-censorship resistance for users on restricted cellular carriers like MCI and Irancell. 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 8443 and domain masking perform under heavy censorship in Iran and China? ▼
The configuration utilizes port 8443 to provide redundant network ingress for users experiencing regional routing anomalies. Spoofing sovereign regional service yandex.net constitutes an operational flaw that causes immediate connection termination. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.
What steps should I take if node #N (150.241.***.***) 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: 9🔓 4. Service Availability & Anti-Bot Checks (Stash Checks)
| Service | Status | Region | Technical Detail | RTT |
|---|---|---|---|---|
| ChatGPT (web) | ○ error | — | request failed | — |
| ChatGPT (app) | ○ error | — | request failed | — |
| YouTube Premium | ○ error | — | request failed | — |
| Netflix | ○ error | — | request failed | 6003 ms |
| Claude | ○ error | — | 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 | ● error | — | request failed | — |
| Anthropic | Anthropic | ● error | — | request failed | — |
| Google Gemini | ● error | — | request failed | — | |
| 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 Germany VLESS nodes with automatic background updates:
✨ Related Working Nodes
Top verified alternatives with matching protocol and country: