Skip to main content
Tunnel verified at last checkLast result: 2026-10-08 15:56:13 UTC

Connection and verification

Protocol
VLESS
Address
152.70.58.201:443
Transport / security
TCP / REALITY
Last verified exit IP
152.70.58.201
Last verified handshake
301 ms
Last verified HTTPS first byte
486 ms
Download speed
1.651 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-14 03:05:05 UTC
Recorded tunnel checks
10
Successful tunnel checks
10
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)
5760 09-21 16:2010-08 15:56Check time (UTC)
HTTPS first byte (ms)
7740 09-21 16:2010-08 15:56Check time (UTC)

Check history

Latest 15 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 ok301 ms486 ms152.70.58.201
Tunnel ok293 ms473 ms152.70.58.201
Tunnel ok493 ms773 ms152.70.58.201
Tunnel ok576 ms774 ms152.70.58.201
Tunnel ok311 ms498 ms152.70.58.201
Tunnel ok329 ms627 ms152.70.58.201
Tunnel ok315 ms593 ms152.70.58.201
Tunnel ok418 ms603 ms152.70.58.201
Tunnel ok313 ms500 ms152.70.58.201
Tunnel ok362 ms564 ms152.70.58.201
Unsupported checkerNot measuredNot measuredNot verified
Unsupported checkerNot measuredNot measuredNot verified
Unsupported checkerNot measuredNot measuredNot verified
Unsupported checkerNot measuredNot measuredNot verified
Policy blockedNot measuredNot measuredNot verified

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.