Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 07:28:24 UTC

Connection and verification

Protocol
VLESS
Address
46.250.250.149:2053
Transport / security
TCP / REALITY
Last verified exit IP
46.250.250.149
Last verified handshake
923 ms
Last verified HTTPS first byte
1,405 ms
Download speed
2.603 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-14 23:23:50 UTC
Recorded tunnel checks
20
Successful tunnel checks
20
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)
28450 09-14 23:2310-09 07:28Check time (UTC)
HTTPS first byte (ms)
34350 09-14 23:2310-09 07:28Check time (UTC)

Check history

Latest 21 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 ok923 ms1,405 ms46.250.250.149
Tunnel ok970 ms1,467 ms46.250.250.149
Tunnel ok2,845 ms3,435 ms46.250.250.149
Tunnel ok1,076 ms1,595 ms46.250.250.149
Tunnel ok1,065 ms1,605 ms46.250.250.149
Tunnel ok1,267 ms1,869 ms46.250.250.149
Tunnel ok1,057 ms1,565 ms46.250.250.149
Tunnel ok976 ms1,471 ms46.250.250.149
Tunnel ok1,082 ms1,670 ms46.250.250.149
Policy blockedNot measuredNot measuredNot verified
Tunnel ok930 ms1,413 ms46.250.250.149
Tunnel ok1,211 ms1,711 ms46.250.250.149
Tunnel ok958 ms1,457 ms46.250.250.149
Tunnel ok994 ms1,501 ms46.250.250.149
Tunnel ok978 ms1,487 ms46.250.250.149
Tunnel ok957 ms1,450 ms46.250.250.149
Tunnel ok1,162 ms1,685 ms46.250.250.149
Tunnel ok993 ms1,500 ms46.250.250.149
Tunnel ok1,075 ms1,593 ms46.250.250.149
Tunnel ok1,086 ms1,574 ms46.250.250.149
Tunnel ok1,188 ms1,721 ms46.250.250.149

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.