Skip to main content
Tunnel verified at last checkLast result: 2026-10-08 17:39:41 UTC

Connection and verification

Protocol
Trojan
Address
104.21.57.25:443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
51.158.239.186
Last verified handshake
1,291 ms
Last verified HTTPS first byte
1,672 ms
Download speed
2.263 Mbps
Source
Barry Trojan
First recorded check
2026-10-02 23:37:53 UTC
Recorded tunnel checks
7
Successful tunnel checks
5
Recorded tunnel success rate
71.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)
49190 10-02 23:3710-08 17:39Check time (UTC)
HTTPS first byte (ms)
55550 10-02 23:3710-08 17:39Check time (UTC)

Check history

Latest 7 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 ok1,291 ms1,672 ms51.158.239.186
Tunnel failedNot measuredNot measuredNot verified
TimeoutNot measuredNot measuredNot verified
Tunnel ok4,919 ms5,555 ms51.158.239.186
Tunnel ok609 ms876 ms51.158.239.186
Tunnel ok630 ms842 ms51.158.239.186
Tunnel ok349 ms531 ms51.158.239.186

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.