Node No Longer Responding
This server is no longer responding (verified by our checker). Recommended working alternatives:
Poland (PL) — VLESS TCP Node
Host: 144.31.0.140:443 • Tested: 12:50:47 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 |
|---|---|---|---|---|
| Thu, 22 Oct 2026 14:20:47 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 2a09:bac5:5062:246e::3a1:b |
| Thu, 22 Oct 2026 13:50:47 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 2a09:bac5:5062:246e::3a1:b |
| Thu, 22 Oct 2026 12:50:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 390 ms | 2a09:bac5:5062:246e::3a1:b |
| Thu, 22 Oct 2026 12:20:47 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 2a09:bac5:5062:246e::3a1:b |
| Thu, 22 Oct 2026 11:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 331 ms | 2a09:bac5:5065:246e::3a1:b |
| Thu, 22 Oct 2026 10:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 332 ms | 2a09:bac5:5061:246e::3a1:b |
| Thu, 22 Oct 2026 09:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 300 ms | 2a09:bac5:5063:246e::3a1:b |
| Thu, 22 Oct 2026 08:20:48 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 338 ms | 2a09:bac5:5063:2482::3a3:3f |
| Thu, 22 Oct 2026 07:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 294 ms | 2a09:bac5:5066:2482::3a3:3f |
| Thu, 22 Oct 2026 06:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 3102 ms | 2a09:bac5:5067:2478::3a2:4f |
| Thu, 22 Oct 2026 05:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 292 ms | 2a09:bac5:5067:2478::3a2:4f |
| Thu, 22 Oct 2026 04:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 287 ms | 2a09:bac5:5063:2478::3a2:4f |
| Thu, 22 Oct 2026 03:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 323 ms | 2a09:bac5:5063:2478::3a2:4f |
| Thu, 22 Oct 2026 02:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 284 ms | 2a09:bac1:5bc0:40::3a4:6 |
| Thu, 22 Oct 2026 01:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 330 ms | 2a09:bac1:5ba0:40::3a5:7 |
⚙️ Protocol Parameter Specification
Verified protocol configuration attributes required for manual client profiles.
Adaptive Stealth Node (RAW / TCP)
Cryptographic resistance profile and Deep Packet Inspection (DPI) evasion analysis
Node 144.31.***.*** 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.
api.sakhalin.fyi): Employing low-traffic property api.sakhalin.fyi drastically minimizes the probability of synthetic replay attacks by the Great Firewall. ❓ Frequently Asked Questions for Node #18042920
How does node #N bypass state-level censorship and firewall restrictions? ▼
Node 144.31.***.*** 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 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? ▼
Port 443 delivers unmatched survivability across enterprise networks, public university campuses, and mobile data providers. Employing low-traffic property api.sakhalin.fyi drastically minimizes the probability of synthetic replay attacks by the Great Firewall. 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: 14🔓 4. Service Availability & Anti-Bot Checks (Stash Checks)
| Service | Status | Region | Technical Detail | RTT |
|---|---|---|---|---|
| ChatGPT (web) | ○ error | — | request failed | — |
| ChatGPT (app) | ● available | — | — | 1532 ms |
| YouTube Premium | ● available | — | — | 1617 ms |
| Netflix | ○ error | — | request failed | 1110 ms |
| Claude | ○ error | — | Cloudflare challenged the request, so availability was never tested | 1516 ms |
| TikTok | ○ error | — | request failed | — |
| Gemini | ○ error | — | request failed | — |
| NotebookLM | ● available | — | sign-in required | 3308 ms |
🤖 5. AI Model API Endpoints (Direct Probe)
| AI Endpoint | Vendor | State | HTTP | Detail | RTT |
|---|---|---|---|---|---|
| OpenAI | OpenAI | ● error | — | request failed | — |
| Anthropic | Anthropic | ● reachable | 401 | answered, credentials not supplied | 1822 ms |
| Google Gemini | ● reachable | 403 | answered, credentials not supplied | 1513 ms | |
| DeepSeek | DeepSeek | ● reachable | 401 | answered, credentials not supplied | 1836 ms |
| Qwen (Singapore) | Alibaba | ● reachable | 401 | answered, credentials not supplied | 2131 ms |
| Qwen (Beijing) | Alibaba | ● error | — | request failed | — |
| Kimi / Moonshot | Moonshot | ● reachable | 401 | answered, credentials not supplied | 3096 ms |
| 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 Poland VLESS nodes with automatic background updates:
✨ Related Working Nodes
Top verified alternatives with matching protocol and country: