VLESS server free-amsterdam-node-1.cloudwidecdn.com:443
TCP / REALITY · 0xRadikal verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 01:45:06 UTC
Connection and verification
- Protocol
- VLESS
- Address
- free-amsterdam-node-1.cloudwidecdn.com:443
- Transport / security
- TCP / REALITY
- Last verified exit IP
- 86.54.28.75
- Last verified handshake
- 579 ms
- Last verified HTTPS first byte
- 767 ms
- Download speed
- 1.11 Mbps
- Source
- 0xRadikal verified downloadable configs
- First recorded check
- 2026-09-16 12:08:54 UTC
- Recorded tunnel checks
- 20
- Successful tunnel checks
- 20
- 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 21 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 | 579 ms | 767 ms | 86.54.28.75 | |
| Tunnel ok | 619 ms | 814 ms | 86.54.28.75 | |
| Tunnel ok | 573 ms | 759 ms | 86.54.28.75 | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Tunnel ok | 542 ms | 742 ms | 86.54.28.75 | |
| Tunnel ok | 718 ms | 928 ms | 86.54.28.75 | |
| Tunnel ok | 1,060 ms | 1,489 ms | 86.54.28.75 | |
| Tunnel ok | 836 ms | 1,060 ms | 86.54.28.75 | |
| Tunnel ok | 532 ms | 725 ms | 86.54.28.75 | |
| Tunnel ok | 436 ms | 621 ms | 86.54.28.75 | |
| Tunnel ok | 611 ms | 811 ms | 86.54.28.75 | |
| Tunnel ok | 641 ms | 1,080 ms | 86.54.28.75 | |
| Tunnel ok | 316 ms | 499 ms | 86.54.28.75 | |
| Tunnel ok | 367 ms | 563 ms | 86.54.28.75 | |
| Tunnel ok | 506 ms | 703 ms | 86.54.28.75 | |
| Tunnel ok | 644 ms | 843 ms | 86.54.28.75 | |
| Tunnel ok | 705 ms | 901 ms | 86.54.28.75 | |
| Tunnel ok | 416 ms | 611 ms | 86.54.28.75 | |
| Tunnel ok | 658 ms | 1,014 ms | 86.54.28.75 | |
| Tunnel ok | 533 ms | 724 ms | 86.54.28.75 | |
| Tunnel ok | 482 ms | 681 ms | 86.54.28.75 |
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.