🇷🇺 VLESS REALITY Live Verified Node

Russia (RU) — VLESS GRPC Node

Host: 185.179.190.170:59222 • Tested: 7:50:47 PM

Checked Latency 837 ms

Est. Bandwidth 0.0 Mbps

24h Uptime SLA 100%

Exit Consensus RU (Verified)

⚡ Direct Connection URI (VLESS • Russia) Xray-core Verified • 100% Uptime

vless://30572b57-f5ab-4eb8-82d4-a24d399b99f6@185.179.190.170:59222?encryption=none&pbk=riOqDvO6CI06_GP7aJEtDH27zPWu6BiFwGrUESatk1I&security=reality&sid=e03d3096bebd&sni=tbank.ru&type=grpc&fp=chrome#%F0%9F%87%B7%F0%9F%87%BARU-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: 100% (79 probes)

Probe Time	Probe Node	Verdict	Latency (RTT)	Exit IP
Fri, 23 Oct 2026 20:12:08 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	573 ms	2a0a:8d80:0:b1bf::1
Fri, 23 Oct 2026 19:57:06 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	522 ms	2a0a:8d80:0:b1bf::1
Fri, 23 Oct 2026 19:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	837 ms	2a0a:8d80:0:b1bf::1
Fri, 23 Oct 2026 19:17:03 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	445 ms	2a0a:8d80:0:b1bf::1
Fri, 23 Oct 2026 19:12:07 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	1235 ms	2a0a:8d80:0:b1bf::1
Fri, 23 Oct 2026 18:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	422 ms	2a0a:8d80:0:b1bf::1
Fri, 23 Oct 2026 18:32:00 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	575 ms	2a0a:8d80:0:b1bf::1
Fri, 23 Oct 2026 18:22:00 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	606 ms	2a0a:8d80:0:b1bf::1
Fri, 23 Oct 2026 17:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	843 ms	2a0a:8d80:0:b1bf::1
Fri, 23 Oct 2026 17:42:02 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	540 ms	2a0a:8d80:0:b1bf::1
Fri, 23 Oct 2026 17:06:55 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	597 ms	2a0a:8d80:0:b1bf::1
Fri, 23 Oct 2026 17:01:56 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	741 ms	2a0a:8d80:0:b1bf::1
Fri, 23 Oct 2026 16:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	443 ms	2a0a:8d80:0:b1bf::1
Fri, 23 Oct 2026 16:21:53 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	830 ms	2a0a:8d80:0:b1bf::1
Fri, 23 Oct 2026 16:16:55 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	590 ms	2a0a:8d80:0:b1bf::1

⚙️ Protocol Parameter Specification

Verified protocol configuration attributes required for manual client profiles.

Host / Address 185.179.190.170

Port 59222

Security Protocol REALITY

Transport Type GRPC

SNI (Server Name Indication) tbank.ru

Public Key (pbk) riOqDvO6CI06_GP7aJEtDH27zPWu6BiFwGrUESatk1I

Short ID (sid) e03d3096bebd

UUID 30572b57-f5ab-4eb8-82d4-a24d399b99f6

TLS Fingerprint 18013428

🛡️

Hardened Reality Ingress (GRPC)

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

SNI: Regional Enterprise Target (High Routing Discrepancy) Port 59222 (Non-Standard • Heightened Evasion Risk) uTLS: 18013428 Custom Handshake (Active Cloaking)

Featuring high-throughput GRPC connectivity on host 185.179.***.***, the server operates with zero identifiable metadata fingerprints across international borders.

Network Port Analysis: Transmitting over port 59222 risks sudden connection drops when traversing national gateway firewalls that enforce strict protocol whitelists.

SNI Masking Analysis (tbank.ru): Perimeter firewalls flag and terminate external connections claiming domestic domain tbank.ru due to conflicting autonomous system paths.

uTLS Handshake Security Analysis (18013428): The 18013428 emulation profile standardizes cryptographic cipher orderings to resist passive inspection sweeps.

Client Handshake Masking (uTLS): The 18013428 emulation profile standardizes cryptographic cipher orderings to resist passive inspection sweeps.

REALITY Cryptography: Server-pinned Reality key (riOqDvO6CI...) coupled with session ID (e03d3096bebd) guarantees zero-knowledge mutual authorization in Netherlands.

❓ Frequently Asked Questions for Node #18013428

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

Featuring high-throughput GRPC connectivity on host 185.179.***.***, the server operates with zero identifiable metadata fingerprints across international borders. 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 59222 and domain masking perform under heavy censorship in Iran and China? ▼

Transmitting over port 59222 risks sudden connection drops when traversing national gateway firewalls that enforce strict protocol whitelists. Perimeter firewalls flag and terminate external connections claiming domestic domain tbank.ru due to conflicting autonomous system paths. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.

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

1. Exit IP & Autonomous System (Identity) 🇷🇺 RU

Public Exit IPv4: 2a0a:8d80:0:b1bf::1

Network (ASN / Org): AS44094 · Webhost LLC

BGP Prefix / Subnet: —

Node Location: Moscow, Moscow — 🇷🇺 RU

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

Address Class: 🖥️ Hosting / Datacenter

Risk Score:

20 / 100 (95% conf)

Detection Flags:

hosting

Operator / Provider: Webhost LLC

3. Geolocation Consensus (IPv4)

Providers tallied: 18

🇷🇺 RU Russia

100% (18/18)

🔓 4. Service Availability & Anti-Bot Checks (Stash Checks)

Service	Status	Region	Technical Detail	RTT
ChatGPT (web)	● blocked	🇷🇺 RU	the API refused this region	720 ms
ChatGPT (app)	● blocked	🇷🇺 RU	the API refused this region	916 ms
YouTube Premium	● blocked	🇷🇺 RU	not offered in this country	939 ms
Netflix	● blocked	🇷🇺 RU	not offered in this country	916 ms
Claude	● blocked	🇷🇺 RU	the API refused this region	916 ms
TikTok	● blocked	🇷🇺 RU	not offered in this country	—
Gemini	● blocked	🇷🇺 RU	not offered in this country	1178 ms
NotebookLM	● blocked	🇷🇺 RU	not offered in this country	2396 ms

🤖 5. AI Model API Endpoints (Direct Probe)

AI Endpoint	Vendor	State	HTTP	Detail	RTT
OpenAI	OpenAI	● blocked	403	the API refused this region	681 ms
Anthropic	Anthropic	● blocked	403	the API refused this region	980 ms
Google Gemini	Google	● reachable	403	answered, credentials not supplied	792 ms
DeepSeek	DeepSeek	● error	—	request failed	—
Qwen (Singapore)	Alibaba	● reachable	401	answered, credentials not supplied	1363 ms
Qwen (Beijing)	Alibaba	● reachable	401	answered, credentials not supplied	1587 ms
Kimi / Moonshot	Moonshot	● error	—	request failed	—
Zhipu GLM	Zhipu	● reachable	401	answered, credentials not supplied	1241 ms