Node No Longer Responding
This server is no longer responding (verified by our checker). Recommended working alternatives:
United States (US) — VLESS WS Node
Host: 172.67.172.120:443 • Tested: 3:54: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 |
|---|---|---|---|---|
| Wed, 04 Nov 2026 04:07:02 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 2a09:bac5:6d77:e6e::170:107 |
| Wed, 04 Nov 2026 03:54:14 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 40 ms | 2a09:bac5:6d77:e6e::170:107 |
| Wed, 04 Nov 2026 03:17:01 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 383 ms | 2a09:bac5:6d77:e6e::170:107 |
| Wed, 04 Nov 2026 02:54:14 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 452 ms | 83.219.249.189 |
| Wed, 04 Nov 2026 02:44:43 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 2a09:bac5:6d77:e6e::170:107 |
| Wed, 04 Nov 2026 02:28:01 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 433 ms | 2a09:bac5:6d77:e6e::170:107 |
| Wed, 04 Nov 2026 02:16:56 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 794 ms | 2a09:bac5:6d77:e6e::170:107 |
| Wed, 04 Nov 2026 02:11:38 UTC | 🇷🇺 RU Probe | 🟢 HTTP 204 OK | 564 ms | 2a09:bac5:6d77:e6e::170:107 |
| Wed, 04 Nov 2026 01:54:15 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 207 ms | 2a09:bac5:6d77:323c::501:5 |
⚙️ Protocol Parameter Specification
Verified protocol configuration attributes required for manual client profiles.
Direct TLS Encrypted Channel (WS)
Cryptographic resistance profile and Deep Packet Inspection (DPI) evasion analysis
Protected by standard TLS encryption over WS, endpoint 172.67.***.***:443 guarantees private, uncompromised transit through international corridors.
node-link-ac43ef-gw.aareshayad.workers.dev): Utilizing discreet domain node-link-ac43ef-gw.aareshayad.workers.dev enables the proxy tunnel to navigate Iranian and Chinese inspection hardware without triggering suspicion. ❓ Frequently Asked Questions for Node #23457555
How does node #N bypass state-level censorship and firewall restrictions? ▼
Protected by standard TLS encryption over WS, endpoint 172.67.***.***:443 guarantees private, uncompromised transit through international corridors. 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? ▼
Traversing egress routes through port 443 provides maximum reliability since international border firewalls allow encrypted web handshakes unrestricted passage. Utilizing discreet domain node-link-ac43ef-gw.aareshayad.workers.dev enables the proxy tunnel to navigate Iranian and Chinese inspection hardware without triggering suspicion. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.
What steps should I take if node #N (172.67.***.***) 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: 22🔓 4. Service Availability & Anti-Bot Checks (Stash Checks)
| Service | Status | Region | Technical Detail | RTT |
|---|---|---|---|---|
| ChatGPT (web) | ● available | — | — | 804 ms |
| ChatGPT (app) | ● available | — | — | 669 ms |
| YouTube Premium | ● available | — | — | 175 ms |
| Netflix | ● available | 🇺🇸 US | full catalogue | 957 ms |
| Claude | ○ error | — | request failed | — |
| TikTok | ● available | — | — | 1868 ms |
| Gemini | ● available | — | — | 354 ms |
| NotebookLM | ● available | — | sign-in required | 347 ms |
🤖 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 | ● reachable | 403 | answered, credentials not supplied | 218 ms | |
| DeepSeek | DeepSeek | ● reachable | 401 | answered, credentials not supplied | 436 ms |
| Qwen (Singapore) | Alibaba | ● reachable | 401 | answered, credentials not supplied | 1151 ms |
| Qwen (Beijing) | Alibaba | ● reachable | 401 | answered, credentials not supplied | 1165 ms |
| Kimi / Moonshot | Moonshot | ● reachable | 401 | answered, credentials not supplied | 1255 ms |
| Zhipu GLM | Zhipu | ● reachable | 401 | answered, credentials not supplied | 527 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 United States VLESS nodes with automatic background updates:
✨ Related Working Nodes
Top verified alternatives with matching protocol and country: