Trojan server 188.114.97.6:443
WEBSOCKET / TLS · Barry Trojan
Tunnel verified at last checkLast result: 2026-10-23 05:44:18 UTC
Connection and verification
- Protocol
- Trojan
- Address
- 188.114.97.6:443
- Transport / security
- WEBSOCKET / TLS
- Last verified exit IP
- 51.158.239.186
- Last verified handshake
- 434 ms
- Last verified HTTPS first byte
- 645 ms
- Download speed
- 7.107 Mbps
- Source
- Barry Trojan
- First recorded check
- 2026-10-03 02:22:45 UTC
- Recorded tunnel checks
- 19
- Successful tunnel checks
- 15
- Recorded tunnel success rate
- 78.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 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.
| Checked (UTC) | Result | Handshake | HTTPS first byte | Exit IP |
|---|---|---|---|---|
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel ok | 434 ms | 645 ms | 51.158.239.186 | |
| Tunnel ok | 477 ms | 890 ms | 51.158.240.195 | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel ok | 1,499 ms | 1,744 ms | 51.158.239.186 | |
| Tunnel ok | 4,586 ms | 4,900 ms | 51.158.239.186 | |
| Tunnel ok | 2,136 ms | 3,522 ms | 51.158.239.186 | |
| Tunnel ok | 2,486 ms | 3,219 ms | 51.158.239.186 | |
| Tunnel ok | 514 ms | 1,222 ms | 51.158.239.186 | |
| Tunnel ok | 4,334 ms | 4,553 ms | 51.158.239.186 | |
| Tunnel ok | 890 ms | 1,858 ms | 51.158.239.186 | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel ok | 1,221 ms | 1,688 ms | 51.158.239.186 | |
| Tunnel ok | 383 ms | 558 ms | 51.158.239.186 | |
| Tunnel ok | 459 ms | 683 ms | 51.158.239.186 | |
| Tunnel ok | 345 ms | 524 ms | 51.158.239.186 | |
| Tunnel ok | 407 ms | 581 ms | 51.158.239.186 | |
| Tunnel ok | 381 ms | 565 ms | 51.158.239.186 |
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.