VLESS server 3.39.4.109:18967
TCP / REALITY · Au1rxx verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 04:29:42 UTC
Connection and verification
- Protocol
- VLESS
- Address
- 3.39.4.109:18967
- Transport / security
- TCP / REALITY
- Last verified exit IP
- 3.39.4.109
- Last verified handshake
- 821 ms
- Last verified HTTPS first byte
- 1,347 ms
- Download speed
- 2.05 Mbps
- Source
- Au1rxx verified downloadable configs
- First recorded check
- 2026-09-09 19:24:31 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 29 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 | 821 ms | 1,347 ms | 3.39.4.109 | |
| Tunnel ok | 878 ms | 1,747 ms | 3.39.4.109 | |
| Tunnel ok | 854 ms | 1,320 ms | 3.39.4.109 | |
| Tunnel ok | 699 ms | 1,112 ms | 3.39.4.109 | |
| Tunnel ok | 755 ms | 1,217 ms | 3.39.4.109 | |
| Tunnel ok | 703 ms | 1,175 ms | 3.39.4.109 | |
| Tunnel ok | 769 ms | 1,232 ms | 3.39.4.109 | |
| Tunnel ok | 1,587 ms | 2,083 ms | 3.39.4.109 | |
| Tunnel ok | 1,073 ms | 1,651 ms | 3.39.4.109 | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel ok | 686 ms | 1,147 ms | 3.39.4.109 | |
| Tunnel ok | 787 ms | 1,238 ms | 3.39.4.109 | |
| Tunnel ok | 1,524 ms | 1,967 ms | 3.39.4.109 | |
| Tunnel ok | 670 ms | 1,107 ms | 3.39.4.109 | |
| Tunnel ok | 695 ms | 1,145 ms | 3.39.4.109 | |
| Tunnel ok | 676 ms | 1,118 ms | 3.39.4.109 | |
| Tunnel ok | 652 ms | 1,091 ms | 3.39.4.109 | |
| Tunnel ok | 1,212 ms | 1,844 ms | 3.39.4.109 | |
| 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 | |
| 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 | |
| Policy blocked | 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.