VLESS server 137.184.218.169:36925
TCP / REALITY · Au1rxx verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 06:25:20 UTC
Connection and verification
- Protocol
- VLESS
- Address
- 137.184.218.169:36925
- Transport / security
- TCP / REALITY
- Last verified exit IP
- 137.184.218.169
- Last verified handshake
- 530 ms
- Last verified HTTPS first byte
- 702 ms
- Download speed
- Not measured
- Source
- Au1rxx verified downloadable configs
- First recorded check
- 2026-09-13 19:25:08 UTC
- Recorded tunnel checks
- 17
- Successful tunnel checks
- 17
- 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 25 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 | 530 ms | 702 ms | 137.184.218.169 | |
| Tunnel ok | 504 ms | 675 ms | 137.184.218.169 | |
| Tunnel ok | 521 ms | 689 ms | 137.184.218.169 | |
| Tunnel ok | 698 ms | 989 ms | 137.184.218.169 | |
| Tunnel ok | 622 ms | 791 ms | 137.184.218.169 | |
| Tunnel ok | 510 ms | 690 ms | 137.184.218.169 | |
| Tunnel ok | 515 ms | 680 ms | 137.184.218.169 | |
| Tunnel ok | 489 ms | 652 ms | 137.184.218.169 | |
| Tunnel ok | 486 ms | 652 ms | 137.184.218.169 | |
| Tunnel ok | 507 ms | 678 ms | 137.184.218.169 | |
| Tunnel ok | 514 ms | 681 ms | 137.184.218.169 | |
| Tunnel ok | 562 ms | 737 ms | 137.184.218.169 | |
| Tunnel ok | 489 ms | 657 ms | 137.184.218.169 | |
| Tunnel ok | 559 ms | 746 ms | 137.184.218.169 | |
| Tunnel ok | 3,663 ms | 4,261 ms | 137.184.218.169 | |
| Tunnel ok | 511 ms | 681 ms | 137.184.218.169 | |
| Tunnel ok | 544 ms | 730 ms | 137.184.218.169 | |
| 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 |
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.