VLESS server 151.245.106.49:2053
TCP / REALITY · Au1rxx verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 02:17:24 UTC
Connection and verification
- Protocol
- VLESS
- Address
- 151.245.106.49:2053
- Transport / security
- TCP / REALITY
- Last verified exit IP
- 151.245.106.49
- Last verified handshake
- 2,508 ms
- Last verified HTTPS first byte
- 3,061 ms
- Download speed
- 1.846 Mbps
- Source
- Au1rxx verified downloadable configs
- First recorded check
- 2026-09-13 18:43:15 UTC
- Recorded tunnel checks
- 26
- Successful tunnel checks
- 18
- Recorded tunnel success rate
- 69.2%
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 26 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,508 ms | 3,061 ms | 151.245.106.49 | |
| Tunnel ok | 2,628 ms | 3,169 ms | 151.245.106.49 | |
| Tunnel ok | 4,980 ms | 5,922 ms | 151.245.106.49 | |
| Tunnel ok | 1,254 ms | 1,849 ms | 151.245.106.49 | |
| Tunnel ok | 1,146 ms | 1,675 ms | 151.245.106.49 | |
| Tunnel ok | 1,111 ms | 3,118 ms | 151.245.106.49 | |
| Tunnel ok | 2,935 ms | 4,582 ms | 151.245.106.49 | |
| Tunnel ok | 1,754 ms | 2,329 ms | 151.245.106.49 | |
| Tunnel ok | 1,759 ms | 3,469 ms | 151.245.106.49 | |
| Tunnel ok | 3,245 ms | 5,031 ms | 151.245.106.49 | |
| Tunnel ok | 1,238 ms | 2,088 ms | 151.245.106.49 | |
| Tunnel ok | 1,084 ms | 1,631 ms | 151.245.106.49 | |
| Tunnel ok | 1,548 ms | 2,075 ms | 151.245.106.49 | |
| Tunnel ok | 3,091 ms | 6,342 ms | 151.245.106.49 | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel ok | 1,046 ms | 1,558 ms | 151.245.106.49 | |
| Tunnel ok | 1,239 ms | 1,780 ms | 151.245.106.49 | |
| Tunnel ok | 1,263 ms | 1,842 ms | 151.245.106.49 | |
| Tunnel ok | 1,141 ms | 1,680 ms | 151.245.106.49 |
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.