Node No Longer Responding
This server is no longer responding (verified by our checker). Recommended working alternatives:
Japan (JP) — VMESS TCP Node
Host: oc.imfun.fun:18112 • Tested: 1:21: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 15:21:43 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 161.33.185.151 |
| Wed, 21 Oct 2026 14:51:43 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 161.33.185.151 |
| Wed, 21 Oct 2026 14:21:43 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 161.33.185.151 |
| Wed, 21 Oct 2026 13:21:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 3527 ms | 161.33.185.151 |
| Wed, 21 Oct 2026 12:21:43 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 161.33.185.151 |
| Wed, 21 Oct 2026 11:21:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 2500 ms | 161.33.185.151 |
| Wed, 21 Oct 2026 10:51:43 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 161.33.185.151 |
| Wed, 21 Oct 2026 10:21:43 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 161.33.185.151 |
| Wed, 21 Oct 2026 09:13:40 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 929 ms | 161.33.185.151 |
| Wed, 21 Oct 2026 07:25:21 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 161.33.185.151 |
| Wed, 21 Oct 2026 06:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 161.33.185.151 |
| Wed, 21 Oct 2026 06:25:21 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 161.33.185.151 |
| Wed, 21 Oct 2026 05:25:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 3735 ms | 161.33.185.151 |
| Wed, 21 Oct 2026 04:25:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 753 ms | 161.33.185.151 |
| Wed, 21 Oct 2026 02:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 161.33.185.151 |
⚙️ Protocol Parameter Specification
Verified protocol configuration attributes required for manual client profiles.
Standard VMESS Proxy Relay
Cryptographic resistance profile and Deep Packet Inspection (DPI) evasion analysis
Node node-***.imfun.fun delivers dependable VMESS routing through Netherlands with consistent data rates.
❓ Frequently Asked Questions for Node #13785430
How does node #N bypass state-level censorship and firewall restrictions? ▼
Node node-***.imfun.fun delivers dependable VMESS routing through Netherlands with consistent data rates. 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 VMESS 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 18112 and domain masking perform under heavy censorship in Iran and China? ▼
Restricted institutional networks and airport Wi-Fi access points routinely sever connections bound for non-conventional ports like 18112. Discreet masking evades detection. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.
What steps should I take if node #N (node-***.imfun.fun) 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: 8🔓 4. Service Availability & Anti-Bot Checks (Stash Checks)
| Service | Status | Region | Technical Detail | RTT |
|---|---|---|---|---|
| ChatGPT (web) | ○ error | — | request failed | — |
| ChatGPT (app) | ○ error | — | request failed | — |
| YouTube Premium | ○ error | — | request failed | — |
| Netflix | ○ error | — | request failed | 6001 ms |
| Claude | ○ error | — | Cloudflare challenged the request, so availability was never tested | 3801 ms |
| TikTok | ○ error | — | request failed | — |
| Gemini | ○ error | — | AI endpoint unreachable | 3866 ms |
| 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 | ● error | — | request failed | — |
| Zhipu GLM | Zhipu | ● error | — | request failed | — |
🗺️ 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 Japan VMESS nodes with automatic background updates:
✨ Related Working Nodes
Top verified alternatives with matching protocol and country: