Skip to main content
Inactive — did not pass verificationLast result: 2026-10-08 12:08:57 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
104.19.164.155:443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
129.146.86.61
Last verified handshake
6,322 ms
Last verified HTTPS first byte
7,636 ms
Download speed
Not measured
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-27 09:24:20 UTC
Recorded tunnel checks
10
Successful tunnel checks
7
Recorded tunnel success rate
70.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)
137880 09-28 09:4010-08 12:08Check time (UTC)
HTTPS first byte (ms)
151250 09-28 09:4010-08 12:08Check time (UTC)

Check history

Latest 12 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 ok6,322 ms7,636 ms129.146.86.61
Tunnel ok5,913 ms6,813 ms129.146.86.61
Tunnel ok2,458 ms4,161 ms129.146.86.61
Tunnel ok4,923 ms6,474 ms129.146.86.61
Tunnel ok13,788 ms15,125 ms129.146.86.61
Tunnel ok3,850 ms4,432 ms129.146.86.61
TimeoutNot measuredNot measuredNot verified
Policy blockedNot measuredNot measuredNot verified
Policy blockedNot measuredNot measuredNot verified
TimeoutNot measuredNot measuredNot verified
Tunnel ok3,966 ms4,640 ms129.146.86.61
TimeoutNot 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.