Trojan server 188.114.97.6:443
WEBSOCKET / TLS · Barry Trojan
Inactive — did not pass verificationLast result: 2026-10-22 17:44:23 UTC
This endpoint has no current downloadable verification, or a newer check did not succeed. Previous measurements below are historical. Choose another checked Trojan server.
Connection and verification
- Protocol
- Trojan
- Address
- 188.114.97.6:443
- Transport / security
- WEBSOCKET / TLS
- Last verified exit IP
- 51.158.179.253
- Last verified handshake
- 2,596 ms
- Last verified HTTPS first byte
- 2,872 ms
- Download speed
- 2.413 Mbps
- Source
- Barry Trojan
- First recorded check
- 2026-10-02 02:08:23 UTC
- Recorded tunnel checks
- 18
- Successful tunnel checks
- 14
- Recorded tunnel success rate
- 77.8%
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 20 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 |
|---|---|---|---|---|
| Policy blocked | Not measured | Not measured | Not verified | |
| Tunnel ok | 2,596 ms | 2,872 ms | 51.158.179.253 | |
| Tunnel ok | 1,666 ms | 1,916 ms | 51.158.179.253 | |
| Tunnel ok | 7,639 ms | 7,819 ms | 51.158.170.123 | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 1,381 ms | 1,564 ms | 51.158.170.123 | |
| Tunnel ok | 346 ms | 526 ms | 51.158.170.123 | |
| Tunnel ok | 1,546 ms | 1,946 ms | 51.158.170.123 | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 377 ms | 562 ms | 51.158.170.123 | |
| Tunnel ok | 340 ms | 530 ms | 51.158.170.123 | |
| Tunnel ok | 351 ms | 530 ms | 51.158.170.123 | |
| Timeout | Not measured | Not measured | Not verified | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 7,513 ms | 7,683 ms | 51.158.170.123 | |
| Tunnel ok | 325 ms | 499 ms | 51.158.170.123 | |
| Tunnel ok | 335 ms | 513 ms | 51.158.170.123 | |
| Tunnel ok | 373 ms | 551 ms | 51.158.170.123 | |
| Tunnel ok | 317 ms | 490 ms | 51.158.170.123 | |
| Policy blocked | Not measured | Not measured | Not verified |
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.
This saved detail page remains available with its check history. Search indexing requires current successful full-tunnel verification, real measurements and an available configuration.