VMess server pahobac.org:443
WEBSOCKET / TLS · Barry VMess
Tunnel verified at last checkLast result: 2026-10-09 02:52:26 UTC
Connection and verification
- Protocol
- VMess
- Address
- pahobac.org:443
- Transport / security
- WEBSOCKET / TLS
- Last verified exit IP
- 186.190.211.67
- Last verified handshake
- 838 ms
- Last verified HTTPS first byte
- 1,036 ms
- Download speed
- Not measured
- Source
- Barry VMess
- First recorded check
- 2026-09-21 22:11:39 UTC
- Recorded tunnel checks
- 17
- Successful tunnel checks
- 15
- Recorded tunnel success rate
- 88.2%
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 ok | 838 ms | 1,036 ms | 186.190.211.67 | |
| Tunnel ok | 2,416 ms | 2,646 ms | 186.190.211.67 | |
| Tunnel ok | 5,592 ms | 6,161 ms | 186.190.211.67 | |
| Preflight ok | Not measured | Not measured | Not verified | |
| Tunnel ok | 5,899 ms | 6,079 ms | 186.190.211.67 | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 2,666 ms | 3,110 ms | 186.190.211.67 | |
| Tunnel ok | 967 ms | 1,154 ms | 186.190.211.67 | |
| Tunnel ok | 8,202 ms | 9,559 ms | 186.190.211.67 | |
| Preflight ok | Not measured | Not measured | Not verified | |
| Tunnel ok | 681 ms | 881 ms | 139.64.166.25 | |
| Tunnel ok | 1,165 ms | 1,358 ms | 186.190.211.67 | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel ok | 910 ms | 1,088 ms | 186.190.211.67 | |
| Tunnel ok | 1,577 ms | 1,794 ms | 139.64.166.25 | |
| Tunnel ok | 1,163 ms | 1,397 ms | 139.64.166.25 | |
| Tunnel ok | 574 ms | 786 ms | 139.64.166.25 | |
| Tunnel ok | 882 ms | 1,086 ms | 139.64.166.25 | |
| Tunnel ok | 692 ms | 898 ms | 139.64.166.25 |
No recorded checks match this filter.
How to use this VMess configuration
- Download the current configuration while a fresh verification is available.
- Import it into a VMess-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 VMess 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 VMess guide, our checking methodology and public VPN risks.