VLESS server prep.wwwinternetvideo.click:443
TCP / REALITY · rjsxrd secure tunnel-tested configs
Tunnel verified at last checkLast result: 2026-10-09 03:24:52 UTC
Connection and verification
- Protocol
- VLESS
- Address
- prep.wwwinternetvideo.click:443
- Transport / security
- TCP / REALITY
- Last verified exit IP
- 45.13.186.30
- Last verified handshake
- 455 ms
- Last verified HTTPS first byte
- 670 ms
- Download speed
- 2.457 Mbps
- Source
- rjsxrd secure tunnel-tested configs
- First recorded check
- 2026-09-17 19:30:08 UTC
- Recorded tunnel checks
- 21
- Successful tunnel checks
- 21
- 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 23 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 | 455 ms | 670 ms | 45.13.186.30 | |
| Tunnel ok | 426 ms | 703 ms | 45.13.186.30 | |
| Tunnel ok | 1,515 ms | 2,352 ms | 45.13.186.30 | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Tunnel ok | 3,285 ms | 3,754 ms | 45.13.186.30 | |
| Tunnel ok | 1,266 ms | 1,644 ms | 45.13.186.30 | |
| Tunnel ok | 1,558 ms | 1,937 ms | 45.13.186.30 | |
| Tunnel ok | 5,283 ms | 6,584 ms | 45.13.186.30 | |
| Tunnel ok | 3,137 ms | 3,662 ms | 45.13.186.30 | |
| Tunnel ok | 498 ms | 905 ms | 45.13.186.30 | |
| Preflight ok | Not measured | Not measured | Not verified | |
| Tunnel ok | 755 ms | 958 ms | 45.13.186.30 | |
| Tunnel ok | 453 ms | 681 ms | 45.13.186.30 | |
| Tunnel ok | 960 ms | 1,172 ms | 45.13.186.30 | |
| Tunnel ok | 619 ms | 845 ms | 45.13.186.30 | |
| Tunnel ok | 588 ms | 790 ms | 45.13.186.30 | |
| Tunnel ok | 826 ms | 1,061 ms | 45.13.186.30 | |
| Tunnel ok | 861 ms | 1,064 ms | 193.148.57.60 | |
| Tunnel ok | 784 ms | 1,022 ms | 193.148.57.60 | |
| Tunnel ok | 505 ms | 709 ms | 193.148.57.60 | |
| Tunnel ok | 501 ms | 701 ms | 193.148.57.60 | |
| Tunnel ok | 501 ms | 699 ms | 193.148.57.60 | |
| Tunnel ok | 928 ms | 1,237 ms | 193.148.57.60 |
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.