VMess server 172.67.161.144:8443
WEBSOCKET / TLS · Iran Intranet Access verified configs
Inactive — did not pass verificationLast result: 2026-10-19 09:27:29 UTC
This endpoint has no current downloadable verification, or a newer check did not succeed. Previous measurements below are historical. Choose another checked VMess server.
Connection and verification
- Protocol
- VMess
- Address
- 172.67.161.144:8443
- Transport / security
- WEBSOCKET / TLS
- Last verified exit IP
- 207.244.230.92
- Last verified handshake
- 1,384 ms
- Last verified HTTPS first byte
- 1,867 ms
- Download speed
- 2.164 Mbps
- Source
- Iran Intranet Access verified configs
- First recorded check
- 2026-09-14 09:34:15 UTC
- Recorded tunnel checks
- 21
- Successful tunnel checks
- 12
- Recorded tunnel success rate
- 57.1%
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 21 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 | 1,384 ms | 1,867 ms | 207.244.230.92 | |
| Tunnel ok | 1,450 ms | 1,840 ms | 207.244.230.92 | |
| Tunnel ok | 1,563 ms | 1,983 ms | 207.244.230.92 | |
| Tunnel ok | 1,680 ms | 2,092 ms | 207.244.230.92 | |
| Tunnel ok | 1,406 ms | 1,854 ms | 207.244.230.92 | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 2,353 ms | 4,033 ms | 207.244.230.92 | |
| Tunnel ok | 7,556 ms | 9,867 ms | 207.244.230.92 | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 5,651 ms | 6,150 ms | 207.244.230.92 | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 11,396 ms | 13,110 ms | 207.244.230.92 | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel ok | 11,330 ms | 11,794 ms | 207.244.230.92 | |
| Tunnel ok | 14,775 ms | 15,573 ms | 207.244.230.92 | |
| Tunnel ok | 6,967 ms | 7,424 ms | 207.244.230.92 |
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.
This saved detail page remains available with its check history. Search indexing requires current successful full-tunnel verification, real measurements and an available configuration.