Node No Longer Responding
This server is no longer responding (verified by our checker). Recommended working alternatives:
ES (ES) — VLESS TCP Node
Host: 145.249.109.112:27311 • Tested: 3: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 |
|---|---|---|---|---|
| Tue, 20 Oct 2026 22:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 145.249.109.112 |
| Tue, 20 Oct 2026 18:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 145.249.109.112 |
| Tue, 20 Oct 2026 17:25:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 145.249.109.112 |
| Tue, 20 Oct 2026 16:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 145.249.109.112 |
| Tue, 20 Oct 2026 16:25:22 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 145.249.109.112 |
| Tue, 20 Oct 2026 15:25:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 633 ms | 145.249.109.112 |
| Tue, 20 Oct 2026 14:25:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 326 ms | 145.249.109.112 |
| Tue, 20 Oct 2026 13:25:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 310 ms | 145.249.109.112 |
| Tue, 20 Oct 2026 12:25:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 399 ms | 145.249.109.112 |
| Tue, 20 Oct 2026 11:25:21 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 648 ms | 145.249.109.112 |
| Tue, 20 Oct 2026 10:25:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 648 ms | 145.249.109.112 |
| Tue, 20 Oct 2026 09:25:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 815 ms | 145.249.109.112 |
| Tue, 20 Oct 2026 08:25:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 328 ms | 145.249.109.112 |
| Tue, 20 Oct 2026 07:25:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 535 ms | 145.249.109.112 |
| Tue, 20 Oct 2026 06:25:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 633 ms | 145.249.109.112 |
⚙️ 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
Engineered for rigorous perimeter defense, the node at 145.249.***.***:27311 successfully masks proxy sessions as authentic web communications to neutral overseas destinations.
metrika.yandex.ru): Routing engines easily expose false associations with domain metrika.yandex.ru by validating border gateway protocol origin advertisements. ❓ Frequently Asked Questions for Node #15745858
How does node #N bypass state-level censorship and firewall restrictions? ▼
Engineered for rigorous perimeter defense, the node at 145.249.***.***:27311 successfully masks proxy sessions as authentic web communications to neutral overseas destinations. 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 27311 and domain masking perform under heavy censorship in Iran and China? ▼
Port 27311 is highly susceptible to automated firewall blacklisting due to anomalous socket behavior outside traditional web ports. Routing engines easily expose false associations with domain metrika.yandex.ru by validating border gateway protocol origin advertisements. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.
What steps should I take if node #N (145.249.***.***) 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: 24🔓 4. Service Availability & Anti-Bot Checks (Stash Checks)
| Service | Status | Region | Technical Detail | RTT |
|---|---|---|---|---|
| ChatGPT (web) | ● blocked | — | unsupported country | 818 ms |
| ChatGPT (app) | ● available | — | — | 623 ms |
| YouTube Premium | ● blocked | 🇷🇺 RU | not offered in this country | 781 ms |
| Netflix | ● available | 🇪🇸 ES | full catalogue | 1727 ms |
| Claude | ○ error | 🇪🇸 ES | Cloudflare challenged the request, so availability was never tested | 108 ms |
| TikTok | ● blocked | 🇷🇺 RU | not offered in this country | 956 ms |
| Gemini | ● blocked | 🇷🇺 RU | not offered in this country | — |
| NotebookLM | ● blocked | 🇷🇺 RU | not offered in this country | 2209 ms |
🤖 5. AI Model API Endpoints (Direct Probe)
| AI Endpoint | Vendor | State | HTTP | Detail | RTT |
|---|---|---|---|---|---|
| OpenAI | OpenAI | ● reachable | 401 | answered, credentials not supplied | 771 ms |
| Anthropic | Anthropic | ● reachable | 401 | answered, credentials not supplied | 724 ms |
| Google Gemini | ● reachable | 403 | answered, credentials not supplied | 708 ms | |
| DeepSeek | DeepSeek | ● reachable | 401 | answered, credentials not supplied | 820 ms |
| Qwen (Singapore) | Alibaba | ● reachable | 401 | answered, credentials not supplied | 1141 ms |
| Qwen (Beijing) | Alibaba | ● error | — | request failed | — |
| Kimi / Moonshot | Moonshot | ● reachable | 401 | answered, credentials not supplied | 2515 ms |
| Zhipu GLM | Zhipu | ● reachable | 401 | answered, credentials not supplied | 920 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 ES VLESS nodes with automatic background updates:
✨ Related Working Nodes
Top verified alternatives with matching protocol and country: