VLESS server 217.217.254.126:2053
TCP / REALITY · Au1rxx verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 08:10:18 UTC
Connection and verification
- Protocol
- VLESS
- Address
- 217.217.254.126:2053
- Transport / security
- TCP / REALITY
- Last verified exit IP
- 217.217.254.126
- Last verified handshake
- 2,162 ms
- Last verified HTTPS first byte
- 3,037 ms
- Download speed
- 1.05 Mbps
- Source
- Au1rxx verified downloadable configs
- First recorded check
- 2026-09-17 04:21:32 UTC
- Recorded tunnel checks
- 18
- Successful tunnel checks
- 17
- Recorded tunnel success rate
- 94.4%
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 23 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 | 2,162 ms | 3,037 ms | 217.217.254.126 | |
| Tunnel ok | 729 ms | 1,218 ms | 217.217.254.126 | |
| Tunnel ok | 1,141 ms | 1,621 ms | 217.217.254.126 | |
| Tunnel ok | 795 ms | 1,278 ms | 217.217.254.126 | |
| Tunnel ok | 1,399 ms | 1,988 ms | 217.217.254.126 | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 1,707 ms | 2,390 ms | 217.217.254.126 | |
| Tunnel ok | 1,066 ms | 1,658 ms | 217.217.254.126 | |
| Tunnel ok | 816 ms | 1,384 ms | 217.217.254.126 | |
| Tunnel ok | 1,167 ms | 1,672 ms | 217.217.254.126 | |
| Tunnel ok | 752 ms | 1,265 ms | 217.217.254.126 | |
| Tunnel ok | 1,373 ms | 2,010 ms | 217.217.254.126 | |
| Tunnel ok | 892 ms | 1,393 ms | 217.217.254.126 | |
| Tunnel ok | 1,012 ms | 1,885 ms | 217.217.254.126 | |
| Tunnel ok | 866 ms | 1,451 ms | 217.217.254.126 | |
| Tunnel ok | 798 ms | 1,353 ms | 217.217.254.126 | |
| Tunnel ok | 781 ms | 1,292 ms | 217.217.254.126 | |
| Tunnel ok | 1,105 ms | 1,706 ms | 217.217.254.126 | |
| Unsupported checker | Not measured | Not measured | Not verified | |
| Unsupported checker | Not measured | Not measured | Not verified | |
| Unsupported checker | Not measured | Not measured | Not verified | |
| Unsupported checker | Not measured | Not measured | Not verified | |
| Unsupported checker | Not measured | Not measured | Not verified |
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.