Skip to main content
Tunnel verified at last checkLast result: 2026-10-22 12:55:13 UTC

Connection and verification

Protocol
Hysteria2
Address
clash2.deep-links.com:443
Transport / security
UDP / TLS
Last verified exit IP
3.12.34.194
Last verified handshake
4,010 ms
Last verified HTTPS first byte
4,210 ms
Download speed
4.443 Mbps
Source
GetFreeProxy Hysteria2
First recorded check
2026-09-12 17:53:21 UTC
Recorded tunnel checks
13
Successful tunnel checks
2
Recorded tunnel success rate
15.4%

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)
40100 10-20 21:2810-22 12:55Check time (UTC)
HTTPS first byte (ms)
42100 10-20 21:2810-22 12:55Check time (UTC)

Check history

Latest 13 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 Hysteria2 checks, newest first
Checked (UTC)ResultHandshakeHTTPS first byteExit IP
Tunnel ok4,010 ms4,210 ms3.12.34.194
Tunnel ok576 ms778 ms3.12.34.194
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified

How to use this Hysteria2 configuration

  1. Download the current configuration while a fresh verification is available.
  2. Import it into a Hysteria2-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 Hysteria2 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 Hysteria2 guide, our checking methodology and public VPN risks.