VLESS server 36a466g.fi1.h1clayd.click:443

Connection and verification

Protocol

VLESS

Address

36a466g.fi1.h1clayd.click:443

Transport / security

GRPC / REALITY

Last verified exit IP

2.29.101.158

Last verified handshake

11,626 ms

Last verified HTTPS first byte

11,928 ms

Download speed

Not measured

Source

rjsxrd secure tunnel-tested configs

First recorded check

2026-10-17 05:45:46 UTC

Recorded tunnel checks

3

Successful tunnel checks

2

Recorded tunnel success rate

66.7%

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 3 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.

No recorded checks match this filter.

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.