Node No Longer Responding
This server is no longer responding (verified by our checker). Recommended working alternatives:
BG (BG) — VLESS TCP Node
Host: 193.23.195.37:23443 • Tested: 1:51:43 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 |
|---|---|---|---|---|
| Wed, 21 Oct 2026 18:50:47 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 2.27.105.78 |
| Wed, 21 Oct 2026 15:51:43 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 2.27.105.78 |
| Wed, 21 Oct 2026 15:21:43 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 2.27.105.78 |
| Wed, 21 Oct 2026 14:51:43 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 2.27.105.78 |
| Wed, 21 Oct 2026 13:51:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 694 ms | 2.27.105.78 |
| Wed, 21 Oct 2026 12:51:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1226 ms | 2.27.105.78 |
| Wed, 21 Oct 2026 11:51:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 3950 ms | 2.27.105.78 |
| Wed, 21 Oct 2026 10:51:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1512 ms | 2.27.105.78 |
| Wed, 21 Oct 2026 09:51:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1492 ms | 2.27.105.78 |
| Wed, 21 Oct 2026 08:55:14 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1231 ms | 2.27.105.78 |
| Wed, 21 Oct 2026 07:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 683 ms | 2.27.105.78 |
| Wed, 21 Oct 2026 06:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 759 ms | 2.27.105.78 |
| Wed, 21 Oct 2026 05:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 791 ms | 2.27.105.78 |
| Wed, 21 Oct 2026 04:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 815 ms | 2.27.105.78 |
| Wed, 21 Oct 2026 03:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1095 ms | 2.27.105.78 |
⚙️ 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
Node 193.23.***.*** 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.
dzen.ru): Attempting camouflage with domain dzen.ru outside its native jurisdiction results in rapid packet discarding by border inspection units. ❓ Frequently Asked Questions for Node #17060606
How does node #N bypass state-level censorship and firewall restrictions? ▼
Node 193.23.***.*** 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 23443 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 (23443) sessions during localized internet blackouts. Attempting camouflage with domain dzen.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 (193.23.***.***) 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: 25🔓 4. Service Availability & Anti-Bot Checks (Stash Checks)
| Service | Status | Region | Technical Detail | RTT |
|---|---|---|---|---|
| ChatGPT (web) | ● available | — | — | 1712 ms |
| ChatGPT (app) | ● available | — | — | 1556 ms |
| YouTube Premium | ● available | — | — | 1686 ms |
| Netflix | ● available | 🇧🇬 BG | full catalogue | 3067 ms |
| Claude | ○ error | 🇧🇬 BG | Cloudflare challenged the request, so availability was never tested | 319 ms |
| TikTok | ● available | — | — | 2007 ms |
| Gemini | ● available | — | — | 1876 ms |
| NotebookLM | ● available | — | sign-in required | 3584 ms |
🤖 5. AI Model API Endpoints (Direct Probe)
| AI Endpoint | Vendor | State | HTTP | Detail | RTT |
|---|---|---|---|---|---|
| OpenAI | OpenAI | ● reachable | 401 | answered, credentials not supplied | 1714 ms |
| Anthropic | Anthropic | ● reachable | 401 | answered, credentials not supplied | 1669 ms |
| Google Gemini | ● reachable | 403 | answered, credentials not supplied | 1667 ms | |
| DeepSeek | DeepSeek | ● reachable | 401 | answered, credentials not supplied | 1855 ms |
| Qwen (Singapore) | Alibaba | ● reachable | 401 | answered, credentials not supplied | 2183 ms |
| Qwen (Beijing) | Alibaba | ● reachable | 401 | answered, credentials not supplied | 2352 ms |
| Kimi / Moonshot | Moonshot | ● error | — | request failed | — |
| Zhipu GLM | Zhipu | ● reachable | 401 | answered, credentials not supplied | 2361 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 BG VLESS nodes with automatic background updates:
✨ Related Working Nodes
Top verified alternatives with matching protocol and country: