VLESS server 3.39.4.109:13672
TCP / REALITY · Au1rxx verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 06:14:50 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
- 721 ms
- Last verified HTTPS first byte
- 1,132 ms
- Download speed
- 3.168 Mbps
- Source
- Au1rxx verified downloadable configs
- First recorded check
- 2026-09-14 04:38:35 UTC
- Recorded tunnel checks
- 26
- Successful tunnel checks
- 26
- 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 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 | 721 ms | 1,132 ms | 3.39.4.109 | |
| Tunnel ok | 715 ms | 1,136 ms | 3.39.4.109 | |
| Tunnel ok | 2,347 ms | 2,861 ms | 3.39.4.109 | |
| Tunnel ok | 805 ms | 1,219 ms | 3.39.4.109 | |
| Tunnel ok | 828 ms | 1,245 ms | 3.39.4.109 | |
| Tunnel ok | 721 ms | 1,175 ms | 3.39.4.109 | |
| Tunnel ok | 682 ms | 1,093 ms | 3.39.4.109 | |
| Tunnel ok | 1,342 ms | 1,883 ms | 3.39.4.109 | |
| Tunnel ok | 734 ms | 1,271 ms | 3.39.4.109 | |
| Tunnel ok | 736 ms | 1,205 ms | 3.39.4.109 | |
| Tunnel ok | 689 ms | 1,154 ms | 3.39.4.109 | |
| Tunnel ok | 801 ms | 1,252 ms | 3.39.4.109 | |
| Tunnel ok | 732 ms | 1,305 ms | 3.39.4.109 | |
| Tunnel ok | 685 ms | 1,207 ms | 3.39.4.109 | |
| Tunnel ok | 682 ms | 1,129 ms | 3.39.4.109 | |
| Tunnel ok | 780 ms | 1,234 ms | 3.39.4.109 | |
| Tunnel ok | 658 ms | 1,115 ms | 3.39.4.109 | |
| Tunnel ok | 711 ms | 1,132 ms | 3.39.4.109 | |
| Tunnel ok | 843 ms | 1,291 ms | 3.39.4.109 | |
| Tunnel ok | 708 ms | 1,160 ms | 3.39.4.109 | |
| Tunnel ok | 692 ms | 1,158 ms | 3.39.4.109 | |
| Tunnel ok | 670 ms | 1,109 ms | 3.39.4.109 | |
| Tunnel ok | 781 ms | 1,381 ms | 3.39.4.109 | |
| Tunnel ok | 682 ms | 1,132 ms | 3.39.4.109 | |
| Tunnel ok | 787 ms | 1,269 ms | 3.39.4.109 | |
| Tunnel ok | 834 ms | 1,324 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.