Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 05:08:28 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
887 ms
Last verified HTTPS first byte
1,124 ms
Download speed
1.074 Mbps
Source
rjsxrd secure tunnel-tested configs
First recorded check
2026-09-18 05:09:41 UTC
Recorded tunnel checks
20
Successful tunnel checks
16
Recorded tunnel success rate
80.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.

Tunnel handshake (ms)
34020 09-20 13:5210-09 05:08Check time (UTC)
HTTPS first byte (ms)
39460 09-20 13:5210-09 05:08Check time (UTC)

Check history

Latest 20 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.

Recorded VLESS checks, newest first
Checked (UTC)ResultHandshakeHTTPS first byteExit IP
Tunnel ok887 ms1,124 ms45.13.186.30
Tunnel ok474 ms843 ms45.13.186.30
Tunnel ok3,402 ms3,946 ms45.13.186.30
TimeoutNot measuredNot measuredNot verified
Tunnel ok523 ms748 ms45.13.186.30
Tunnel ok855 ms1,086 ms45.13.186.30
Tunnel ok833 ms1,047 ms45.13.186.30
Tunnel ok2,615 ms3,507 ms45.13.186.30
TimeoutNot measuredNot measuredNot verified
Tunnel ok471 ms678 ms45.13.186.30
Tunnel ok809 ms1,009 ms45.13.186.30
Tunnel ok550 ms764 ms45.13.186.30
Tunnel ok471 ms700 ms45.13.186.30
Tunnel ok480 ms892 ms45.13.186.30
Tunnel ok1,362 ms1,775 ms45.13.186.30
Tunnel ok526 ms946 ms45.13.186.30
Tunnel ok596 ms860 ms193.148.57.60
TimeoutNot measuredNot measuredNot verified
Tunnel ok584 ms811 ms193.148.57.60
TimeoutNot measuredNot measuredNot verified

How to use this VLESS configuration

  1. Download the current configuration while a fresh verification is available.
  2. Import it into a VLESS-compatible client, preserving all required transport, security and authentication parameters.
  3. 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.