🇯🇵 VLESS Live Verified Node

Japan (JP) — VLESS WS Node

Host: 212.135.212.211:443 • Tested: 2:51:43 PM

Checked Latency 426 ms

Est. Bandwidth 0.0 Mbps

24h Uptime SLA 95.8%

Exit Consensus JP (Verified)

⚡ Direct Connection URI (VLESS • Japan) Xray-core Verified • 95.8% Uptime

vless://495c7195-85b8-498a-bf20-2ea9ce9175b5@212.135.212.211:443?encryption=none&security=tls&type=ws&host=snip.edgeoneai.cc.cd&path=%2Ffdip%3Dsstp%3A%2F%2Fvpn%3Avpn%40public-vpn-200.opengw.net%3A443%3Fed%3D2560fp%3Dchromefp%3Dchrome&sni=snip.edgeoneai.cc.cd&fp=chrome#%F0%9F%87%AF%F0%9F%87%B5JP-freevpnkeys.com-TG-%40yavpn_robot

1. Direct Single Key Copy the URI above into Happ, Incy, v2RayTun, or v2rayNG. Re-tested every 30 min.

2. Free Auto-Updating Subscription Auto-sync fresh working nodes every 30 min: https://freevpnkeys.com/sub/happ

3. Private 10 Gbps Anti-DPI Multi-Key Need zero congestion, 10 Gbps speed & strict ISP whitelist bypass? Get a private key in Telegram bot @yavpn_robot (~$0.05/day).

⚡ 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:

Happ ↗

iOS / Android / PC / Mac

v2RayTun ↗

Android / iOS / PC / Mac

Incy ↗

iOS / Android / PC / Mac

v2rayNG ↗

Android

FlClashX / Clash ↗

Windows / macOS / Android

Karing / sing-box ↗

Core / GUI

📊 Recent Verification History

Automated multi-point health probes through Xray-core / libxray (verified every 30 minutes)

24h SLA: 95.8% (24 probes)

Probe Time	Probe Node	Verdict	Latency (RTT)	Exit IP
Wed, 21 Oct 2026 14:51:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	426 ms	2a09:bac5:4436:2787::3f0:49
Wed, 21 Oct 2026 13:51:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	832 ms	2a09:bac5:4436:1deb::2fb:35
Wed, 21 Oct 2026 12:51:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	530 ms	2a09:bac5:4436:1191::1c0:234
Wed, 21 Oct 2026 11:51:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1449 ms	2a09:bac5:4436:2787::3f0:30
Wed, 21 Oct 2026 10:51:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	633 ms	2a09:bac5:58e6:323::50:18c
Wed, 21 Oct 2026 09:51:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1063 ms	2a09:bac5:4436:2791::3f1:68
Wed, 21 Oct 2026 08:55:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	922 ms	2a09:bac5:4436:2791::3f1:47
Wed, 21 Oct 2026 07:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	951 ms	2a09:bac5:4316:1e14::2ff:5
Wed, 21 Oct 2026 07:25:21 UTC	🇺🇸 US Main	🔴 Failed (timeout_or_captive_portal)	—	2a09:bac5:4436:2787::3f0:49
Wed, 21 Oct 2026 06:25:21 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	732 ms	2a09:bac5:4436:1deb::2fb:a
Wed, 21 Oct 2026 05:25:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1138 ms	2a09:bac5:4436:2787::3f0:9
Wed, 21 Oct 2026 04:25:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	590 ms	2a09:bac5:4436:2e0a::496:6
Wed, 21 Oct 2026 03:25:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	529 ms	2a09:bac5:4436:2e00::495:7
Wed, 21 Oct 2026 02:25:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	746 ms	2a09:bac5:4436:1000::198:9e
Wed, 21 Oct 2026 01:25:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	596 ms	2a09:bac5:4436:2787::3f0:12

⚙️ Protocol Parameter Specification

Verified protocol configuration attributes required for manual client profiles.

Host / Address 212.135.212.211

Port 443

Security Protocol TLS

Transport Type WS

SNI (Server Name Indication) snip.edgeoneai.cc.cd

Path /fdip=sstp://vpn:vpn@public-vpn-200.opengw.net:443?ed=2560fp=chromefp=chrome

UUID 495c7195-85b8-498a-bf20-2ea9ce9175b5

TLS Fingerprint 17263313

🛡️

Direct TLS Encrypted Channel (WS)

Cryptographic resistance profile and Deep Packet Inspection (DPI) evasion analysis

SNI: Discreet Camouflage Host (Optimized for Evasion) Port 443 (Universal HTTPS Gateway) uTLS: 17263313 Custom Handshake (Active Cloaking)

Standard TLS deployment over WS on server 212.135.***.*** delivers dependable international throughput with an uptime rating of 99.6%.

Network Port Analysis: With traffic routed across port 443, data packets pass uninhibited through carrier-grade network address translation gateways worldwide.

SNI Masking Analysis (snip.edgeoneai.cc.cd): This discreet camouflage choice (snip.edgeoneai.cc.cd) provides superior operational security for users circumventing severe digital censorship.

uTLS Handshake Security Analysis (17263313): Configured 17263313 parameters ensure client handshakes adhere to accepted cryptographic conventions without alerting middlebox monitors.

Client Handshake Masking (uTLS): Configured 17263313 parameters ensure client handshakes adhere to accepted cryptographic conventions without alerting middlebox monitors.

❓ Frequently Asked Questions for Node #17263313

How does node #N bypass state-level censorship and firewall restrictions? ▼

Standard TLS deployment over WS on server 212.135.***.*** 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 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? ▼

With traffic routed across port 443, data packets pass uninhibited through carrier-grade network address translation gateways worldwide. This discreet camouflage choice (snip.edgeoneai.cc.cd) provides superior operational security for users circumventing severe digital censorship. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.

What steps should I take if node #N (212.135.***.***) 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.

GeoCheck v1.4 ⏱ 18.32s

1. Exit IP & Autonomous System (Identity) 🇯🇵 JP

Public Exit IPv4: 2a09:bac5:4436:2787::3f0:49

Network (ASN / Org): AS13335 · Cloudflare, Inc.

BGP Prefix / Subnet: —

Node Location: Narita, Chiba — 🇯🇵 JP

2. IP Address Reputation (proxycheck.io v3) Hosting

Address Class: 🖥️ Hosting / Datacenter

Risk Score:

20 / 100 (95% conf)

Detection Flags:

hosting

Operator / Provider: Cloudflare, Inc.

3. Geolocation Consensus (IPv4)

Providers tallied: 11

🇯🇵 JP Japan

91% (10/11)

🇺🇸 US United States

9% (1/11)

🔓 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	● available	—	—	5395 ms
Netflix	○ error	—	request failed	6002 ms
Claude	○ error	—	request failed	—
TikTok	● available	—	—	5715 ms
Gemini	● available	—	—	5787 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	Google	● reachable	403	answered, credentials not supplied	3796 ms
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	—