Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 06:40:56 UTC

Connection and verification

Protocol
VLESS
Address
159.89.87.21:28190
Transport / security
TCP / REALITY
Last verified exit IP
159.89.87.21
Last verified handshake
487 ms
Last verified HTTPS first byte
653 ms
Download speed
Not measured
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-22 12:27:06 UTC
Recorded tunnel checks
11
Successful tunnel checks
11
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)
6200 09-22 12:2710-09 06:40Check time (UTC)
HTTPS first byte (ms)
8370 09-22 12:2710-09 06:40Check time (UTC)

Check history

Latest 11 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 ok487 ms653 ms159.89.87.21
Tunnel ok507 ms672 ms159.89.87.21
Tunnel ok515 ms683 ms159.89.87.21
Tunnel ok495 ms665 ms159.89.87.21
Tunnel ok476 ms635 ms159.89.87.21
Tunnel ok496 ms666 ms159.89.87.21
Tunnel ok508 ms683 ms159.89.87.21
Tunnel ok531 ms707 ms159.89.87.21
Tunnel ok487 ms653 ms159.89.87.21
Tunnel ok516 ms696 ms159.89.87.21
Tunnel ok620 ms837 ms159.89.87.21

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.