VLESS server 46.250.250.149:2053
TCP / REALITY · Au1rxx verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 06:24:48 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
- 978 ms
- Last verified HTTPS first byte
- 1,466 ms
- Download speed
- 2.715 Mbps
- Source
- Au1rxx verified downloadable configs
- First recorded check
- 2026-09-13 03:41:37 UTC
- Recorded tunnel checks
- 25
- Successful tunnel checks
- 25
- 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.
Check history
Latest 25 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.
| Checked (UTC) | Result | Handshake | HTTPS first byte | Exit IP |
|---|---|---|---|---|
| Tunnel ok | 978 ms | 1,466 ms | 46.250.250.149 | |
| Tunnel ok | 1,067 ms | 1,563 ms | 46.250.250.149 | |
| Tunnel ok | 914 ms | 1,491 ms | 46.250.250.149 | |
| Tunnel ok | 1,062 ms | 1,557 ms | 46.250.250.149 | |
| Tunnel ok | 1,493 ms | 1,991 ms | 46.250.250.149 | |
| Tunnel ok | 947 ms | 1,427 ms | 46.250.250.149 | |
| Tunnel ok | 1,073 ms | 1,592 ms | 46.250.250.149 | |
| Tunnel ok | 971 ms | 1,454 ms | 46.250.250.149 | |
| Tunnel ok | 971 ms | 1,466 ms | 46.250.250.149 | |
| Tunnel ok | 927 ms | 1,411 ms | 46.250.250.149 | |
| Tunnel ok | 956 ms | 1,433 ms | 46.250.250.149 | |
| Tunnel ok | 964 ms | 1,461 ms | 46.250.250.149 | |
| Tunnel ok | 1,457 ms | 1,957 ms | 46.250.250.149 | |
| Tunnel ok | 1,204 ms | 1,741 ms | 46.250.250.149 | |
| Tunnel ok | 3,416 ms | 3,895 ms | 46.250.250.149 | |
| Tunnel ok | 1,070 ms | 1,574 ms | 46.250.250.149 | |
| Tunnel ok | 1,453 ms | 2,118 ms | 46.250.250.149 | |
| Tunnel ok | 1,005 ms | 1,515 ms | 46.250.250.149 | |
| Tunnel ok | 974 ms | 1,475 ms | 46.250.250.149 | |
| Tunnel ok | 986 ms | 1,490 ms | 46.250.250.149 | |
| Tunnel ok | 1,117 ms | 1,655 ms | 46.250.250.149 | |
| Tunnel ok | 1,169 ms | 1,688 ms | 46.250.250.149 | |
| Tunnel ok | 2,003 ms | 3,061 ms | 46.250.250.149 | |
| Tunnel ok | 1,172 ms | 1,734 ms | 46.250.250.149 | |
| Tunnel ok | 1,180 ms | 1,730 ms | 46.250.250.149 |
No recorded checks match this filter.
How to use this VLESS configuration
- Download the current configuration while a fresh verification is available.
- Import it into a VLESS-compatible client, preserving all required transport, security and authentication parameters.
- 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.