Skip to main content
Tunnel verified at last checkLast result: 2026-10-08 17:40:59 UTC

Connection and verification

Protocol
VLESS
Address
2.59.253.251:443
Transport / security
TCP / REALITY
Last verified exit IP
2.59.253.251
Last verified handshake
265 ms
Last verified HTTPS first byte
474 ms
Download speed
10.624 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-21 08:43:28 UTC
Recorded tunnel checks
17
Successful tunnel checks
15
Recorded tunnel success rate
88.2%

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)
3430 09-21 08:4310-08 17:40Check time (UTC)
HTTPS first byte (ms)
6180 09-21 08:4310-08 17:40Check time (UTC)

Check history

Latest 17 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 ok265 ms474 ms2.59.253.251
Tunnel ok276 ms458 ms2.59.253.251
Tunnel ok295 ms491 ms2.59.253.251
Tunnel ok323 ms540 ms2.59.253.251
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok321 ms539 ms2.59.253.251
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok325 ms544 ms2.59.253.251
Tunnel ok317 ms544 ms2.59.253.251
Tunnel ok334 ms552 ms2.59.253.251
Tunnel ok342 ms556 ms2.59.253.251
Tunnel ok321 ms534 ms2.59.253.251
Tunnel ok322 ms543 ms2.59.253.251
Tunnel ok312 ms524 ms2.59.253.251
Tunnel ok338 ms571 ms2.59.253.251
Tunnel ok343 ms618 ms2.59.253.251
Tunnel ok337 ms554 ms2.59.253.251

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.