Node No Longer Responding
This server is no longer responding (verified by our checker). Recommended working alternatives:
NO (NO) — VLESS TCP Node
Host: 144.31.217.148:443 • Tested: 10:24:14 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 10:24:14 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1281 ms | 31.76.5.153 |
| Tue, 03 Nov 2026 09:57:29 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 31.76.5.153 |
| Tue, 03 Nov 2026 09:36:38 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 31.76.5.153 |
| Tue, 03 Nov 2026 09:24:14 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 496 ms | 31.76.5.153 |
| Tue, 03 Nov 2026 09:04:04 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 324 ms | 31.76.5.153 |
| Tue, 03 Nov 2026 08:53:35 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 31.76.5.153 |
| Tue, 03 Nov 2026 08:37:24 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 293 ms | 31.76.5.153 |
| Tue, 03 Nov 2026 08:26:54 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 5471 ms | 31.76.5.153 |
| Tue, 03 Nov 2026 08:24:15 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 775 ms | 31.76.5.153 |
| Tue, 03 Nov 2026 08:21:15 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 372 ms | 31.76.5.153 |
| Tue, 03 Nov 2026 08:05:00 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 1452 ms | 31.76.5.153 |
| Tue, 03 Nov 2026 07:59:48 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 4550 ms | 31.76.5.153 |
| Tue, 03 Nov 2026 07:44:02 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 3394 ms | 31.76.5.153 |
| Tue, 03 Nov 2026 07:33:01 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 1556 ms | 31.76.5.153 |
| Tue, 03 Nov 2026 07:24:14 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 3711 ms | 31.76.5.153 |
⚙️ Protocol Parameter Specification
Verified protocol configuration attributes required for manual client profiles.
Zero-Signature Reality Relay (RAW / TCP)
Cryptographic resistance profile and Deep Packet Inspection (DPI) evasion analysis
Configured with advanced Reality evasion protocols over RAW / TCP, endpoint 144.31.***.***:443 ensures sustained packet throughput through aggressive firewalls.
norvegia29838199399293838.izzzyvpn.space): Masking under unobtrusive host norvegia29838199399293838.izzzyvpn.space ensures outstanding longevity across mobile networks operated by MCI, Irancell, and Rightel. ❓ Frequently Asked Questions for Node #23209705
How does node #N bypass state-level censorship and firewall restrictions? ▼
Configured with advanced Reality evasion protocols over RAW / TCP, endpoint 144.31.***.***:443 ensures sustained packet throughput through aggressive firewalls. 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 norvegia29838199399293838.izzzyvpn.space 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 (144.31.***.***) 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: 16🔓 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 | 4397 ms |
| Claude | ○ error | — | request failed | — |
| TikTok | ● available | — | — | 2912 ms |
| 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 | ● reachable | 401 | answered, credentials not supplied | 3499 ms |
| Qwen (Singapore) | Alibaba | ● error | — | request failed | — |
| Qwen (Beijing) | Alibaba | ● error | — | request failed | — |
| Kimi / Moonshot | Moonshot | ● error | — | request failed | — |
| Zhipu GLM | Zhipu | ● reachable | 401 | answered, credentials not supplied | 3122 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 NO VLESS nodes with automatic background updates:
✨ Related Working Nodes
Top verified alternatives with matching protocol and country: