VLESS server 3.39.4.109:13672
TCP / REALITY · Au1rxx verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 04:25:51 UTC
Connection and verification
- Protocol
- VLESS
- Address
- 3.39.4.109:13672
- Transport / security
- TCP / REALITY
- Last verified exit IP
- 3.39.4.109
- Last verified handshake
- 741 ms
- Last verified HTTPS first byte
- 1,189 ms
- Download speed
- 3.306 Mbps
- Source
- Au1rxx verified downloadable configs
- First recorded check
- 2026-09-13 19:22:50 UTC
- Recorded tunnel checks
- 26
- Successful tunnel checks
- 25
- Recorded tunnel success rate
- 96.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 | 741 ms | 1,189 ms | 3.39.4.109 | |
| Tunnel ok | 1,264 ms | 1,818 ms | 3.39.4.109 | |
| Tunnel ok | 1,116 ms | 1,746 ms | 3.39.4.109 | |
| Tunnel ok | 754 ms | 1,166 ms | 3.39.4.109 | |
| Tunnel ok | 751 ms | 1,165 ms | 3.39.4.109 | |
| Tunnel ok | 724 ms | 1,196 ms | 3.39.4.109 | |
| Tunnel ok | 714 ms | 1,266 ms | 3.39.4.109 | |
| Tunnel ok | 1,858 ms | 2,379 ms | 3.39.4.109 | |
| Tunnel ok | 1,061 ms | 1,692 ms | 3.39.4.109 | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 661 ms | 1,101 ms | 3.39.4.109 | |
| Tunnel ok | 1,122 ms | 1,572 ms | 3.39.4.109 | |
| Tunnel ok | 740 ms | 1,610 ms | 3.39.4.109 | |
| Tunnel ok | 1,301 ms | 1,745 ms | 3.39.4.109 | |
| Tunnel ok | 671 ms | 1,538 ms | 3.39.4.109 | |
| Tunnel ok | 726 ms | 1,173 ms | 3.39.4.109 | |
| Tunnel ok | 683 ms | 1,131 ms | 3.39.4.109 | |
| Tunnel ok | 732 ms | 1,177 ms | 3.39.4.109 | |
| Tunnel ok | 689 ms | 1,138 ms | 3.39.4.109 | |
| Tunnel ok | 702 ms | 1,582 ms | 3.39.4.109 | |
| Tunnel ok | 708 ms | 1,153 ms | 3.39.4.109 | |
| Tunnel ok | 698 ms | 1,145 ms | 3.39.4.109 | |
| Tunnel ok | 696 ms | 1,151 ms | 3.39.4.109 | |
| Tunnel ok | 822 ms | 1,311 ms | 3.39.4.109 | |
| Tunnel ok | 794 ms | 1,273 ms | 3.39.4.109 | |
| Tunnel ok | 761 ms | 1,232 ms | 3.39.4.109 |
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.