Trojan server 104.16.71.213:443
WEBSOCKET / TLS · 0xRadikal verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-22 17:34:44 UTC
Connection and verification
- Protocol
- Trojan
- Address
- 104.16.71.213:443
- Transport / security
- WEBSOCKET / TLS
- Last verified exit IP
- 51.159.148.230
- Last verified handshake
- 370 ms
- Last verified HTTPS first byte
- 563 ms
- Download speed
- 6.142 Mbps
- Source
- 0xRadikal verified downloadable configs
- First recorded check
- 2026-09-12 09:42:29 UTC
- Recorded tunnel checks
- 26
- Successful tunnel checks
- 15
- Recorded tunnel success rate
- 57.7%
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 29 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 ok | 370 ms | 563 ms | 51.159.148.230 | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 411 ms | 611 ms | 51.159.167.67 | |
| Tunnel ok | 390 ms | 582 ms | 51.159.148.230 | |
| Tunnel ok | 1,391 ms | 1,578 ms | 51.159.148.230 | |
| Tunnel ok | 376 ms | 568 ms | 51.159.148.230 | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 344 ms | 531 ms | 51.159.148.230 | |
| Tunnel ok | 367 ms | 561 ms | 51.159.148.230 | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 358 ms | 545 ms | 51.159.148.230 | |
| Tunnel ok | 374 ms | 583 ms | 51.159.148.230 | |
| Tunnel ok | 8,587 ms | 8,788 ms | 51.159.148.230 | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 430 ms | 621 ms | 51.159.148.230 | |
| Tunnel ok | 390 ms | 584 ms | 51.159.148.230 | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Timeout | Not measured | Not measured | Not verified | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel ok | 448 ms | 644 ms | 51.159.162.83 | |
| Preflight ok | Not measured | Not measured | Not verified | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 367 ms | 560 ms | 51.159.162.83 | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel ok | 419 ms | 615 ms | 51.15.130.70 |
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.