VLESS server 156.246.88.125:26518
TCP / REALITY · 0xRadikal verified downloadable configs
Inactive — did not pass verificationLast result: 2026-10-09 00:54:30 UTC
This endpoint has no current downloadable verification, or a newer check did not succeed. Previous measurements below are historical. Choose another checked VLESS server.
Connection and verification
- Protocol
- VLESS
- Address
- 156.246.88.125:26518
- Transport / security
- TCP / REALITY
- Last verified exit IP
- 156.246.88.125
- Last verified handshake
- 8,341 ms
- Last verified HTTPS first byte
- 9,289 ms
- Download speed
- Not measured
- Source
- 0xRadikal verified downloadable configs
- First recorded check
- 2026-09-14 16:56:09 UTC
- Recorded tunnel checks
- 15
- Successful tunnel checks
- 12
- Recorded tunnel success rate
- 80.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 18 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 | 8,341 ms | 9,289 ms | 156.246.88.125 | |
| Timeout | Not measured | Not measured | Not verified | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Tunnel ok | 1,026 ms | 1,521 ms | 156.246.88.125 | |
| Tunnel ok | 968 ms | 1,466 ms | 156.246.88.125 | |
| Tunnel ok | 2,419 ms | 4,100 ms | 156.246.88.125 | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 1,160 ms | 1,699 ms | 156.246.88.125 | |
| Tunnel ok | 1,128 ms | 1,673 ms | 156.246.88.125 | |
| Tunnel ok | 1,067 ms | 1,606 ms | 156.246.88.125 | |
| Tunnel ok | 1,568 ms | 2,819 ms | 156.246.88.125 | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Tunnel ok | 1,061 ms | 1,551 ms | 156.246.88.125 | |
| Tunnel ok | 6,488 ms | 7,804 ms | 156.246.88.125 | |
| Tunnel ok | 1,227 ms | 1,732 ms | 156.246.88.125 | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 1,197 ms | 1,699 ms | 156.246.88.125 |
No recorded checks match this filter.
How to use this VLESS configuration
- Download the current configuration while a fresh verification is available.
- Import it into a VLESS-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 VLESS 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 VLESS guide, our checking methodology and public VPN risks.