Trojan server 104.17.147.22:443
WEBSOCKET / TLS · 0xRadikal verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-22 16:35:15 UTC
Connection and verification
- Protocol
- Trojan
- Address
- 104.17.147.22:443
- Transport / security
- WEBSOCKET / TLS
- Last verified exit IP
- 51.159.148.230
- Last verified handshake
- 800 ms
- Last verified HTTPS first byte
- 1,073 ms
- Download speed
- 5.537 Mbps
- Source
- 0xRadikal verified downloadable configs
- First recorded check
- 2026-09-17 09:11:00 UTC
- Recorded tunnel checks
- 25
- Successful tunnel checks
- 16
- Recorded tunnel success rate
- 64.0%
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 27 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 | 800 ms | 1,073 ms | 51.159.148.230 | |
| Tunnel ok | 2,396 ms | 2,583 ms | 51.159.167.67 | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 324 ms | 509 ms | 51.159.148.230 | |
| Tunnel ok | 360 ms | 549 ms | 51.159.148.230 | |
| Tunnel ok | 360 ms | 539 ms | 51.159.148.230 | |
| Tunnel ok | 466 ms | 693 ms | 51.159.148.230 | |
| Tunnel ok | 377 ms | 563 ms | 51.159.148.230 | |
| Tunnel ok | 319 ms | 505 ms | 51.159.148.230 | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 356 ms | 553 ms | 51.159.148.230 | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 396 ms | 586 ms | 51.159.148.230 | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel ok | 7,700 ms | 7,883 ms | 51.159.148.230 | |
| Tunnel ok | 466 ms | 657 ms | 51.159.148.230 | |
| Tunnel ok | 364 ms | 553 ms | 51.159.148.230 | |
| Tunnel ok | 381 ms | 571 ms | 51.159.148.230 | |
| Tunnel ok | 341 ms | 527 ms | 51.159.148.230 | |
| Tunnel ok | 6,561 ms | 6,934 ms | 51.159.162.83 | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Timeout | Not measured | Not measured | Not verified | |
| Timeout | Not measured | Not measured | Not verified | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Timeout | 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.