⚠️

Node No Longer Responding

This server is no longer responding (verified by our checker). Recommended working alternatives:

🇷🇺 WEBPROXY RU (477ms) → 🇷🇺 WEBPROXY RU (509ms) → 🇷🇺 WEBPROXY RU (686ms) →

🇷🇺 WEBPROXY Server Sleeping / Dead

Russia (RU) — WEBPROXY WS Node

Host: w.ultra-fast.cc:443 • Tested: 7:25:20 AM

✈️ Open in Telegram

Checked Latency Offline / Timeout

Est. Bandwidth 0 Mbps

24h Uptime SLA 0% (Inactive)

Exit Consensus RU (Unreachable)

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

✈️ Open in Telegram ↗

Telegram Desktop / iOS / Android

🌐 t.me/webproxy Link ↗

Universal Web Redirect

📊 Recent Verification History

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

24h SLA: 77.8% (27 probes)

Probe Time	Probe Node	Verdict	Latency (RTT)	Exit IP
Tue, 20 Oct 2026 08:55:20 UTC	🇺🇸 US Main	🔴 Failed (unreachable)	—	158.160.140.14
Tue, 20 Oct 2026 08:25:20 UTC	🇺🇸 US Main	🔴 Failed (unreachable)	—	158.160.140.14
Tue, 20 Oct 2026 07:25:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	924 ms	158.160.140.14
Tue, 20 Oct 2026 06:25:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	779 ms	158.160.140.14
Tue, 20 Oct 2026 05:55:20 UTC	🇺🇸 US Main	🔴 Failed (unreachable)	—	158.160.140.14
Tue, 20 Oct 2026 04:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	808 ms	158.160.140.14
Tue, 20 Oct 2026 04:25:20 UTC	🇺🇸 US Main	🔴 Failed (unreachable)	—	158.160.140.14
Tue, 20 Oct 2026 03:25:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1541 ms	158.160.140.14
Tue, 20 Oct 2026 02:55:20 UTC	🇺🇸 US Main	🔴 Failed (unreachable)	—	158.160.140.14
Tue, 20 Oct 2026 01:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	595 ms	158.160.140.14
Tue, 20 Oct 2026 00:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	580 ms	158.160.140.14
Mon, 19 Oct 2026 23:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	579 ms	158.160.140.14
Mon, 19 Oct 2026 22:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	627 ms	158.160.140.14
Mon, 19 Oct 2026 22:25:20 UTC	🇺🇸 US Main	🔴 Failed (unreachable)	—	158.160.140.14
Mon, 19 Oct 2026 21:25:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	585 ms	158.160.140.14

⚙️ Protocol Parameter Specification

Verified protocol configuration attributes required for manual client profiles.

Host / Address w.ultra-fast.cc

Port 443

Security Protocol TLS

Transport Type WS

SNI (Server Name Indication) w.ultra-fast.cc

Secret ddeb2176532a2ba0efd4d61127957ee30d

🛡️

Telegram WEB-Proxy (HTTPS / WebSocket Bridge)

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

SNI: Direct Match (Standard TLS) Port 443 (Standard HTTPS) uTLS: Telegram WebView (Native HTTPS)

Native Telegram WEB-Proxy (tproxy-server / telemt) operating over standard HTTPS port 443 with HMAC-SHA256 bridge authentication and WebSocket transport.

Network Port Analysis: Port 443 is the universal standard for secure HTTPS traffic. Firewalls and ISPs cannot block it without disrupting regular web access.

SNI Masking Analysis (w.ultra-fast.cc): SNI matches target server hostname — clean standard TLS handshake with no cross-domain mismatch.

uTLS Handshake Security Analysis (Native Telegram WebView): Native Telegram WEB-Proxy uses the authentic system WebView HTTPS/WebSocket TLS stack on port 443, indistinguishable from regular web traffic.

Client Handshake Masking (uTLS): Native Telegram WEB-Proxy uses the authentic system WebView HTTPS/WebSocket TLS stack on port 443, indistinguishable from regular web traffic.

❓ Frequently Asked Questions for Node #14706860

How does the TLS security profile protect my connection? ▼

Native Telegram WEB-Proxy (tproxy-server / telemt) operating over standard HTTPS port 443 with HMAC-SHA256 bridge authentication and WebSocket transport.

What client apps are recommended for this WEBPROXY key? ▼

We recommend modern clients supporting VLESS Reality and Vision: Happ, Incy, v2RayTun, FlClashX, Koala Clash, Karing, and v2rayNG.

What should I do if this server stops responding? ▼

Free public keys are updated and re-verified automatically every 15-30 minutes. If this key goes offline, use our 1-click subscription link to always receive only fresh, currently responsive servers.

🌐 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 ⏱ 0.41s

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

Public Exit IPv4: 158.160.140.14

Network (ASN / Org): AS200350 · Yandex.Cloud LLC

BGP Prefix / Subnet: —

Node Location: Moscow (Tsentralnyy administrativnyy okrug), 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: Yandex.Cloud LLC

3. Geolocation Consensus (IPv4)

Providers tallied: 9

🇷🇺 RU Russia

100% (9/9)

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

Service	Status	Region	Technical Detail	RTT
ChatGPT (web)	○ untested	—	awaiting tunnel probe	—
Claude (Anthropic)	○ untested	—	awaiting tunnel probe	—
Google Gemini	○ untested	—	awaiting tunnel probe	—
Google NotebookLM	○ untested	—	awaiting tunnel probe	—
YouTube Premium	○ untested	—	awaiting tunnel probe	—
Netflix	○ untested	—	awaiting tunnel probe	—
TikTok	○ untested	—	awaiting tunnel probe	—