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

Connection and verification

Protocol
Trojan
Address
www.speedtest.net:443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
51.159.148.230
Last verified handshake
349 ms
Last verified HTTPS first byte
535 ms
Download speed
7.292 Mbps
Source
Barry Trojan
First recorded check
2026-10-02 23:37:38 UTC
Recorded tunnel checks
19
Successful tunnel checks
11
Recorded tunnel success rate
57.9%

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)
4710 10-02 23:3710-22 17:20Check time (UTC)
HTTPS first byte (ms)
6550 10-02 23:3710-22 17:20Check time (UTC)

Check history

Latest 19 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 ok349 ms535 ms51.159.148.230
TimeoutNot measuredNot measuredNot verified
Tunnel ok459 ms641 ms51.159.167.67
Tunnel ok343 ms523 ms51.159.148.230
Tunnel ok381 ms581 ms51.159.148.230
Tunnel ok402 ms599 ms51.159.148.230
Tunnel ok358 ms556 ms51.159.148.230
TimeoutNot measuredNot measuredNot verified
Tunnel ok391 ms578 ms51.159.148.230
Tunnel ok362 ms562 ms51.159.148.230
Tunnel ok439 ms622 ms51.159.148.230
Tunnel failedNot measuredNot measuredNot verified
TimeoutNot measuredNot measuredNot verified
TimeoutNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
TimeoutNot measuredNot measuredNot verified
Tunnel ok394 ms579 ms51.159.148.230
TimeoutNot measuredNot measuredNot verified
Tunnel ok471 ms655 ms51.159.148.230

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.