Node No Longer Responding
This server is no longer responding (verified by our checker). Recommended working alternatives:
Poland (PL) — VLESS TCP Node
Host: 80.47.13.138:443 • Tested: 1:12:04 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 |
|---|---|---|---|---|
| Sun, 25 Oct 2026 20:12:04 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 80.47.13.140 |
| Sun, 25 Oct 2026 16:42:04 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 80.47.13.140 |
| Sun, 25 Oct 2026 15:12:04 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 80.47.13.140 |
| Sun, 25 Oct 2026 14:42:04 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 80.47.13.140 |
| Sun, 25 Oct 2026 14:12:04 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 80.47.13.140 |
| Sun, 25 Oct 2026 13:12:04 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 362 ms | 80.47.13.140 |
| Sun, 25 Oct 2026 12:12:04 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 488 ms | 80.47.13.140 |
| Sun, 25 Oct 2026 11:12:04 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 3237 ms | 80.47.13.140 |
| Sun, 25 Oct 2026 10:12:04 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 345 ms | 80.47.13.140 |
| Sun, 25 Oct 2026 09:12:04 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 345 ms | 80.47.13.140 |
| Sun, 25 Oct 2026 08:12:04 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 490 ms | 80.47.13.140 |
| Sun, 25 Oct 2026 07:12:05 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1354 ms | 80.47.13.140 |
| Sun, 25 Oct 2026 06:12:05 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 411 ms | 80.47.13.140 |
| Sun, 25 Oct 2026 05:12:04 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 465 ms | 80.47.13.140 |
| Sun, 25 Oct 2026 04:12:05 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 540 ms | 80.47.13.140 |
⚙️ 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
The endpoint leverages cryptographic Reality camouflage over RAW / TCP to secure international internet access with an observed round-trip latency of 58 ms.
pl1.mycloud1.org): By steering clear of prominent corporate brands, domain pl1.mycloud1.org maintains uninterrupted transit across heavily policed internet pipelines. ❓ Frequently Asked Questions for Node #19141287
How does node #N bypass state-level censorship and firewall restrictions? ▼
The endpoint leverages cryptographic Reality camouflage over RAW / TCP to secure international internet access with an observed round-trip latency of 58 ms. 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? ▼
Using port 443 minimizes transit packet loss and prevents artificial connection resetting on congested undersea fiber cables. By steering clear of prominent corporate brands, domain pl1.mycloud1.org maintains uninterrupted transit across heavily policed internet pipelines. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.
What steps should I take if node #N (80.47.***.***) 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: 26🔓 4. Service Availability & Anti-Bot Checks (Stash Checks)
| Service | Status | Region | Technical Detail | RTT |
|---|---|---|---|---|
| ChatGPT (web) | ● available | — | — | 1673 ms |
| ChatGPT (app) | ● available | — | — | 1090 ms |
| YouTube Premium | ● blocked | 🇷🇺 RU | not offered in this country | 1605 ms |
| Netflix | ● available | 🇵🇱 PL | full catalogue | 2489 ms |
| Claude | ○ error | 🇵🇱 PL | Cloudflare challenged the request, so availability was never tested | 276 ms |
| TikTok | ● available | — | — | 1709 ms |
| Gemini | ● blocked | 🇷🇺 RU | not offered in this country | 2320 ms |
| NotebookLM | ● blocked | 🇷🇺 RU | not offered in this country | 5193 ms |
🤖 5. AI Model API Endpoints (Direct Probe)
| AI Endpoint | Vendor | State | HTTP | Detail | RTT |
|---|---|---|---|---|---|
| OpenAI | OpenAI | ● reachable | 401 | answered, credentials not supplied | 1598 ms |
| Anthropic | Anthropic | ● reachable | 401 | answered, credentials not supplied | 1390 ms |
| Google Gemini | ● reachable | 403 | answered, credentials not supplied | 1835 ms | |
| DeepSeek | DeepSeek | ● reachable | 401 | answered, credentials not supplied | 1599 ms |
| Qwen (Singapore) | Alibaba | ● reachable | 401 | answered, credentials not supplied | 2132 ms |
| Qwen (Beijing) | Alibaba | ● reachable | 401 | answered, credentials not supplied | 1921 ms |
| Kimi / Moonshot | Moonshot | ● reachable | 401 | answered, credentials not supplied | 2430 ms |
| Zhipu GLM | Zhipu | ● reachable | 401 | answered, credentials not supplied | 1608 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 Poland VLESS nodes with automatic background updates:
✨ Related Working Nodes
Top verified alternatives with matching protocol and country: