Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 07:24:44 UTC

Connection and verification

Protocol
VLESS
Address
152.228.139.33:35108
Transport / security
GRPC / REALITY
Last verified exit IP
152.228.139.33
Last verified handshake
350 ms
Last verified HTTPS first byte
546 ms
Download speed
4.749 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-20 19:07:04 UTC
Recorded tunnel checks
18
Successful tunnel checks
18
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)
24170 09-20 19:0710-09 07:24Check time (UTC)
HTTPS first byte (ms)
26990 09-20 19:0710-09 07:24Check time (UTC)

Check history

Latest 18 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 ok350 ms546 ms152.228.139.33
Tunnel ok375 ms605 ms152.228.139.33
Tunnel ok349 ms544 ms152.228.139.33
Tunnel ok376 ms573 ms152.228.139.33
Tunnel ok377 ms570 ms152.228.139.33
Tunnel ok677 ms909 ms152.228.139.33
Tunnel ok331 ms520 ms152.228.139.33
Tunnel ok342 ms539 ms152.228.139.33
Tunnel ok432 ms845 ms152.228.139.33
Tunnel ok358 ms559 ms152.228.139.33
Tunnel ok352 ms549 ms152.228.139.33
Tunnel ok344 ms721 ms152.228.139.33
Tunnel ok347 ms537 ms152.228.139.33
Tunnel ok303 ms486 ms152.228.139.33
Tunnel ok392 ms790 ms152.228.139.33
Tunnel ok419 ms646 ms152.228.139.33
Tunnel ok2,417 ms2,699 ms152.228.139.33
Tunnel ok476 ms678 ms152.228.139.33

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.