Skip to main content
Inactive — did not pass verificationLast result: 2026-10-24 23:16:53 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
31.70.111.146:443
Transport / security
TCP / REALITY
Last verified exit IP
31.70.111.146
Last verified handshake
363 ms
Last verified HTTPS first byte
569 ms
Download speed
6.956 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-10-01 19:22:55 UTC
Recorded tunnel checks
14
Successful tunnel checks
14
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)
28150 10-01 19:2210-24 23:16Check time (UTC)
HTTPS first byte (ms)
31690 10-01 19:2210-24 23:16Check time (UTC)

Check history

Latest 14 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 ok363 ms569 ms31.70.111.146
Tunnel ok319 ms523 ms31.70.111.146
Tunnel ok455 ms662 ms31.70.111.146
Tunnel ok311 ms508 ms31.70.111.146
Tunnel ok310 ms512 ms31.70.111.146
Tunnel ok268 ms453 ms31.70.111.146
Tunnel ok312 ms508 ms31.70.111.146
Tunnel ok300 ms483 ms31.70.111.146
Tunnel ok291 ms474 ms31.70.111.146
Tunnel ok297 ms485 ms31.70.111.146
Tunnel ok314 ms501 ms31.70.111.146
Tunnel ok307 ms498 ms31.70.111.146
Tunnel ok2,815 ms3,169 ms31.70.111.146
Tunnel ok301 ms489 ms31.70.111.146

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.