Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 05:44:45 UTC

Connection and verification

Protocol
Trojan
Address
8.47.69.0:443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
51.158.170.123
Last verified handshake
348 ms
Last verified HTTPS first byte
524 ms
Download speed
8.349 Mbps
Source
Barry Trojan
First recorded check
2026-09-29 15:37:42 UTC
Recorded tunnel checks
11
Successful tunnel checks
6
Recorded tunnel success rate
54.5%

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)
16790 09-29 15:3710-09 05:44Check time (UTC)
HTTPS first byte (ms)
18510 09-29 15:3710-09 05:44Check time (UTC)

Check history

Latest 11 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 ok348 ms524 ms51.158.170.123
Tunnel ok352 ms537 ms51.158.170.123
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
TimeoutNot measuredNot measuredNot verified
TimeoutNot measuredNot measuredNot verified
Tunnel ok598 ms781 ms51.158.170.123
Tunnel ok305 ms498 ms51.158.170.123
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok1,679 ms1,851 ms51.158.170.123
Tunnel ok348 ms533 ms51.158.170.123

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.

This saved detail page remains available with its check history. Search indexing requires current successful full-tunnel verification, real measurements and an available configuration.