Trojan server 8.47.69.0:443
WEBSOCKET / TLS · Barry Trojan
Tunnel verified at last checkLast result: 2026-10-22 14:00:41 UTC
Connection and verification
- Protocol
- Trojan
- Address
- 8.47.69.0:443
- Transport / security
- WEBSOCKET / TLS
- Last verified exit IP
- 51.158.179.253
- Last verified handshake
- 905 ms
- Last verified HTTPS first byte
- 1,210 ms
- Download speed
- Not measured
- Source
- Barry Trojan
- First recorded check
- 2026-09-23 18:43:42 UTC
- Recorded tunnel checks
- 14
- Successful tunnel checks
- 13
- Recorded tunnel success rate
- 92.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.
Check history
Latest 14 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.
| Checked (UTC) | Result | Handshake | HTTPS first byte | Exit IP |
|---|---|---|---|---|
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 905 ms | 1,210 ms | 51.158.179.253 | |
| Tunnel ok | 366 ms | 549 ms | 51.158.179.253 | |
| Tunnel ok | 3,379 ms | 3,575 ms | 51.158.170.123 | |
| Tunnel ok | 3,438 ms | 3,628 ms | 51.158.170.123 | |
| Tunnel ok | 340 ms | 538 ms | 51.158.170.123 | |
| Tunnel ok | 7,480 ms | 7,660 ms | 51.158.170.123 | |
| Tunnel ok | 1,336 ms | 1,512 ms | 51.158.170.123 | |
| Tunnel ok | 319 ms | 498 ms | 51.158.170.123 | |
| Tunnel ok | 391 ms | 572 ms | 51.158.170.123 | |
| Tunnel ok | 7,742 ms | 7,928 ms | 51.158.170.123 | |
| Tunnel ok | 337 ms | 520 ms | 51.158.170.123 | |
| Tunnel ok | 341 ms | 530 ms | 51.158.173.231 | |
| Tunnel ok | 339 ms | 515 ms | 51.158.173.231 |
No recorded checks match this filter.
How to use this Trojan configuration
- Download the current configuration while a fresh verification is available.
- Import it into a Trojan-compatible client, preserving all required transport, security and authentication parameters.
- 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.