Skip to main content
Tunnel verified at last checkLast result: 2026-10-08 21:01:04 UTC

Connection and verification

Protocol
Trojan
Address
104.16.72.41:443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
51.159.148.230
Last verified handshake
3,440 ms
Last verified HTTPS first byte
3,628 ms
Download speed
Not measured
Source
Barry Trojan
First recorded check
2026-09-20 12:14:43 UTC
Recorded tunnel checks
18
Successful tunnel checks
15
Recorded tunnel success rate
83.3%

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)
34400 09-21 11:1410-08 21:01Check time (UTC)
HTTPS first byte (ms)
36280 09-21 11:1410-08 21:01Check time (UTC)

Check history

Latest 18 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 ok3,440 ms3,628 ms51.159.148.230
Tunnel ok391 ms587 ms51.159.148.230
Tunnel ok343 ms528 ms51.159.148.230
Tunnel ok374 ms562 ms51.159.148.230
Tunnel ok373 ms556 ms51.159.148.230
Tunnel ok353 ms531 ms51.159.148.230
Tunnel ok363 ms552 ms51.159.148.230
Tunnel ok350 ms535 ms51.159.148.230
Tunnel ok343 ms532 ms51.159.148.230
Tunnel ok376 ms567 ms51.159.148.230
Tunnel ok401 ms601 ms51.159.148.230
Tunnel ok366 ms550 ms51.159.148.230
Tunnel ok325 ms512 ms51.159.148.230
Tunnel ok397 ms592 ms51.159.162.83
TimeoutNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok371 ms551 ms51.159.162.83
TimeoutNot measuredNot measuredNot verified

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.