Skip to main content
Tunnel verified at last checkLast result: 2026-09-09 17:22:22 UTC

Connection and verification

Protocol
Trojan
Address
8.47.69.0:443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
51.15.126.204
Last verified handshake
420 ms
Last verified HTTPS first byte
676 ms
Download speed
6.403 Mbps
Source
Freedom V2Ray tested configs
First recorded check
2026-09-09 00:51:01 UTC
Recorded tunnel checks
2
Successful tunnel checks
2
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

Tunnel handshake (ms)
4200 2026-09-09 00:51:01 UTC: 341 ms2026-09-09 17:22:22 UTC: 420 ms09-09 00:5109-09 17:22Check time (UTC)
HTTPS first byte (ms)
6760 2026-09-09 00:51:01 UTC: 514 ms2026-09-09 17:22:22 UTC: 676 ms09-09 00:5109-09 17:22Check time (UTC)

Check history

Latest 2 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 Trojan checks, newest first
Checked (UTC)ResultHandshakeHTTPS first byteExit IP
Tunnel ok420 ms676 ms51.15.126.204
Tunnel ok341 ms514 ms51.15.126.204

How to use this Trojan configuration

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