VLESS server 3.39.4.109:13672
TCP / REALITY · Au1rxx verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 05:39:02 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
- 1,042 ms
- Last verified HTTPS first byte
- 1,539 ms
- Download speed
- 1.294 Mbps
- Source
- Au1rxx verified downloadable configs
- First recorded check
- 2026-09-13 09:47:23 UTC
- Recorded tunnel checks
- 24
- Successful tunnel checks
- 24
- 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 24 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 | 1,042 ms | 1,539 ms | 3.39.4.109 | |
| Tunnel ok | 722 ms | 1,546 ms | 3.39.4.109 | |
| Tunnel ok | 815 ms | 1,281 ms | 3.39.4.109 | |
| Tunnel ok | 841 ms | 1,311 ms | 3.39.4.109 | |
| Tunnel ok | 680 ms | 1,103 ms | 3.39.4.109 | |
| Tunnel ok | 679 ms | 1,085 ms | 3.39.4.109 | |
| Tunnel ok | 869 ms | 1,685 ms | 3.39.4.109 | |
| Tunnel ok | 687 ms | 1,130 ms | 3.39.4.109 | |
| Tunnel ok | 688 ms | 1,138 ms | 3.39.4.109 | |
| Tunnel ok | 731 ms | 1,199 ms | 3.39.4.109 | |
| Tunnel ok | 751 ms | 1,219 ms | 3.39.4.109 | |
| Tunnel ok | 783 ms | 1,244 ms | 3.39.4.109 | |
| Tunnel ok | 695 ms | 1,148 ms | 3.39.4.109 | |
| Tunnel ok | 944 ms | 1,409 ms | 3.39.4.109 | |
| Tunnel ok | 761 ms | 1,637 ms | 3.39.4.109 | |
| Tunnel ok | 655 ms | 1,088 ms | 3.39.4.109 | |
| Tunnel ok | 735 ms | 1,237 ms | 3.39.4.109 | |
| Tunnel ok | 697 ms | 1,153 ms | 3.39.4.109 | |
| Tunnel ok | 686 ms | 1,126 ms | 3.39.4.109 | |
| Tunnel ok | 739 ms | 1,187 ms | 3.39.4.109 | |
| Tunnel ok | 669 ms | 1,113 ms | 3.39.4.109 | |
| Tunnel ok | 814 ms | 1,300 ms | 3.39.4.109 | |
| Tunnel ok | 781 ms | 1,258 ms | 3.39.4.109 | |
| Tunnel ok | 923 ms | 1,408 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.