Skip to main content
Inactive — did not pass verificationLast result: 2026-10-09 01:54:08 UTC

This endpoint has no current downloadable verification, or a newer check did not succeed. Previous measurements below are historical. Choose another checked VLESS server.

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
411 ms
Last verified HTTPS first byte
597 ms
Download speed
6.295 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-10 03:43:21 UTC
Recorded tunnel checks
8
Successful tunnel checks
8
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)
4110 09-21 11:0910-09 01:54Check time (UTC)
HTTPS first byte (ms)
5970 09-21 11:0910-09 01:54Check time (UTC)

Check history

Latest 10 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 ok411 ms597 ms152.70.58.201
Tunnel ok278 ms451 ms152.70.58.201
Tunnel ok398 ms585 ms152.70.58.201
Tunnel ok316 ms497 ms152.70.58.201
Tunnel ok377 ms569 ms152.70.58.201
Tunnel ok295 ms474 ms152.70.58.201
Tunnel ok326 ms509 ms152.70.58.201
Tunnel ok331 ms522 ms152.70.58.201
Preflight okNot 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.