Node No Longer Responding
This server is no longer responding (verified by our checker). Recommended working alternatives:
EE (EE) — VLESS TCP Node
Host: 87.242.95.164:8445 • Tested: 8:20:48 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 |
|---|---|---|---|---|
| Fri, 23 Oct 2026 03:50:47 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 13.143.239.237 |
| Thu, 22 Oct 2026 15:20:47 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 13.143.239.237 |
| Thu, 22 Oct 2026 11:50:47 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 13.143.239.237 |
| Thu, 22 Oct 2026 10:20:47 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 13.143.239.237 |
| Thu, 22 Oct 2026 09:50:47 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 13.143.239.237 |
| Thu, 22 Oct 2026 09:20:47 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 13.143.239.237 |
| Thu, 22 Oct 2026 08:20:48 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 435 ms | 13.143.239.237 |
| Thu, 22 Oct 2026 07:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 937 ms | 13.143.239.237 |
| Thu, 22 Oct 2026 06:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 757 ms | 13.143.239.237 |
| Thu, 22 Oct 2026 05:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 2273 ms | 13.143.239.237 |
| Thu, 22 Oct 2026 04:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 943 ms | 13.143.239.237 |
| Thu, 22 Oct 2026 03:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1897 ms | 13.143.239.237 |
| Thu, 22 Oct 2026 02:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 912 ms | 13.143.239.237 |
| Thu, 22 Oct 2026 01:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 656 ms | 13.143.239.237 |
| Thu, 22 Oct 2026 00:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 685 ms | 13.143.239.237 |
⚙️ Protocol Parameter Specification
Verified protocol configuration attributes required for manual client profiles.
Next-Gen VLESS Vision Tunnel
Cryptographic resistance profile and Deep Packet Inspection (DPI) evasion analysis
Featuring high-throughput RAW / TCP connectivity on host 87.242.***.***, the server operates with zero identifiable metadata fingerprints across international borders.
passport.yandex.ru): Attempting camouflage with domain passport.yandex.ru outside its native jurisdiction results in rapid packet discarding by border inspection units. ❓ Frequently Asked Questions for Node #17768051
How does node #N bypass state-level censorship and firewall restrictions? ▼
Featuring high-throughput RAW / TCP connectivity on host 87.242.***.***, the server operates with zero identifiable metadata fingerprints across international borders. 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 8445 and domain masking perform under heavy censorship in Iran and China? ▼
Cellular carriers such as Irancell, Rightel, and China Mobile frequently terminate non-standard port (8445) sessions during localized internet blackouts. Attempting camouflage with domain passport.yandex.ru outside its native jurisdiction results in rapid packet discarding by border inspection units. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.
What steps should I take if node #N (87.242.***.***) 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 | — | — | 3606 ms |
| YouTube Premium | ○ error | — | request failed | — |
| Netflix | ● available | 🇪🇪 EE | full catalogue | 3312 ms |
| Claude | ○ error | — | Cloudflare challenged the request, so availability was never tested | 2797 ms |
| 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 | ● reachable | 401 | answered, credentials not supplied | 3789 ms |
| Zhipu GLM | Zhipu | ● reachable | 401 | answered, credentials not supplied | 2710 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 EE VLESS nodes with automatic background updates:
✨ Related Working Nodes
Top verified alternatives with matching protocol and country: