Node No Longer Responding
This server is no longer responding (verified by our checker). Recommended working alternatives:
TR (TR) — TROJAN WS Node
Host: 104.26.14.137:2053 • Tested: 3:25:20 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, 21 Oct 2026 06:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 153.56.210.134 |
| Wed, 21 Oct 2026 05:25:20 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 153.56.210.134 |
| Wed, 21 Oct 2026 04:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 153.56.210.134 |
| Wed, 21 Oct 2026 04:25:20 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 153.56.210.134 |
| Wed, 21 Oct 2026 03:25:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1187 ms | 153.56.210.134 |
| Wed, 21 Oct 2026 02:25:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 471 ms | 153.56.210.134 |
| Wed, 21 Oct 2026 01:25:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 707 ms | 153.56.210.134 |
| Wed, 21 Oct 2026 00:25:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 629 ms | 153.56.210.134 |
| Tue, 20 Oct 2026 23:25:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 739 ms | 153.56.210.134 |
| Tue, 20 Oct 2026 22:25:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 899 ms | 153.56.210.134 |
| Tue, 20 Oct 2026 21:25:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 544 ms | 153.56.210.134 |
| Tue, 20 Oct 2026 20:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 153.56.210.134 |
| Tue, 20 Oct 2026 19:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 459 ms | 153.56.210.134 |
| Tue, 20 Oct 2026 18:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 555 ms | 153.56.210.134 |
| Tue, 20 Oct 2026 17:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 459 ms | 153.56.210.134 |
⚙️ 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
Standard TLS deployment over WS on server 104.26.***.*** delivers dependable international throughput with an uptime rating of 99.6%.
nimm.mpd.cc.cd.): By steering clear of prominent corporate brands, domain nimm.mpd.cc.cd. maintains uninterrupted transit across heavily policed internet pipelines. ❓ Frequently Asked Questions for Node #5237945
How does node #N bypass state-level censorship and firewall restrictions? ▼
Standard TLS deployment over WS on server 104.26.***.*** delivers dependable international throughput with an uptime rating of 99.6%. 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 TROJAN 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 2053 and domain masking perform under heavy censorship in Iran and China? ▼
The configuration utilizes port 2053 to provide redundant network ingress for users experiencing regional routing anomalies. By steering clear of prominent corporate brands, domain nimm.mpd.cc.cd. 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 (104.26.***.***) 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 | — | — | 2358 ms |
| ChatGPT (app) | ● available | — | — | 2269 ms |
| YouTube Premium | ● blocked | 🇮🇷 IR | not offered in this country | 2376 ms |
| Netflix | ● available | 🇹🇷 TR | full catalogue | 4069 ms |
| Claude | ○ error | 🇹🇷 TR | Cloudflare challenged the request, so availability was never tested | 421 ms |
| TikTok | ● available | — | — | 2572 ms |
| Gemini | ● blocked | 🇮🇷 IR | not offered in this country | 2374 ms |
| NotebookLM | ● blocked | 🇮🇷 IR | not offered in this country | 2170 ms |
🤖 5. AI Model API Endpoints (Direct Probe)
| AI Endpoint | Vendor | State | HTTP | Detail | RTT |
|---|---|---|---|---|---|
| OpenAI | OpenAI | ● reachable | 401 | answered, credentials not supplied | 2282 ms |
| Anthropic | Anthropic | ● reachable | 401 | answered, credentials not supplied | 2156 ms |
| Google Gemini | ● reachable | 403 | answered, credentials not supplied | 2095 ms | |
| DeepSeek | DeepSeek | ● reachable | 401 | answered, credentials not supplied | 2270 ms |
| Qwen (Singapore) | Alibaba | ● reachable | 401 | answered, credentials not supplied | 2863 ms |
| Qwen (Beijing) | Alibaba | ● reachable | 401 | answered, credentials not supplied | 3061 ms |
| Kimi / Moonshot | Moonshot | ● reachable | 401 | answered, credentials not supplied | 3469 ms |
| Zhipu GLM | Zhipu | ● reachable | 401 | answered, credentials not supplied | 3482 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 TR TROJAN nodes with automatic background updates:
✨ Related Working Nodes
Top verified alternatives with matching protocol and country: