Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 03:45:15 UTC

Connection and verification

Protocol
VLESS
Address
146.70.102.82:443
Transport / security
TCP / REALITY
Last verified exit IP
146.70.102.82
Last verified handshake
785 ms
Last verified HTTPS first byte
1,259 ms
Download speed
2.208 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-29 09:25:41 UTC
Recorded tunnel checks
11
Successful tunnel checks
11
Recorded tunnel success rate
100.0%

Handshake is tunnel setup time; HTTPS first byte includes the request through that tunnel. Neither is an ICMP ping or a bandwidth measurement. The success rate covers stored full-tunnel attempts only; it is not continuous uptime.

Performance history

Hover or focus a point for check details. Click or tap to keep them open.

Tunnel handshake (ms)
16850 09-29 09:2510-09 03:45Check time (UTC)
HTTPS first byte (ms)
23690 09-29 09:2510-09 03:45Check time (UTC)

Check history

Latest 11 stored checks, up to 100 per configuration. Checks belong to this configuration’s stable public ID; different configurations on the same host have separate histories. Preflight and policy results do not count as successful tunnels.

Recorded VLESS checks, newest first
Checked (UTC)ResultHandshakeHTTPS first byteExit IP
Tunnel ok785 ms1,259 ms146.70.102.82
Tunnel ok870 ms1,255 ms146.70.102.82
Tunnel ok961 ms1,386 ms146.70.102.82
Tunnel ok956 ms1,369 ms146.70.102.82
Tunnel ok1,193 ms1,587 ms146.70.102.82
Tunnel ok715 ms1,228 ms146.70.102.82
Tunnel ok1,685 ms2,369 ms146.70.102.82
Tunnel ok814 ms1,296 ms146.70.102.82
Tunnel ok709 ms1,180 ms146.70.102.82
Tunnel ok1,230 ms1,741 ms146.70.102.82
Tunnel ok908 ms1,306 ms146.70.102.82

How to use this VLESS configuration

  1. Download the current configuration while a fresh verification is available.
  2. Import it into a VLESS-compatible client, preserving all required transport, security and authentication parameters.
  3. Connect and verify your connection with the IP tool and VPN leak test.

If it fails, compare the latest check time, try a different endpoint or report the problem. Public source configurations can change between checks.

What does a successful check prove?

The external checker completed a VLESS tunnel, carried an HTTPS request and verified a changed public exit IP. This measures technical availability at that time, not the operator’s trustworthiness or performance from your network.

Read the VLESS guide, our checking methodology and public VPN risks.

This saved detail page remains available with its check history. Search indexing requires current successful full-tunnel verification, real measurements and an available configuration.