Skip to main content
Tunnel verified at last checkLast result: 2026-10-22 07:31:52 UTC

Connection and verification

Protocol
VMess
Address
129.146.77.248:39495
Transport / security
WEBSOCKET / NONE
Last verified exit IP
129.146.77.248
Last verified handshake
704 ms
Last verified HTTPS first byte
1,013 ms
Download speed
3.398 Mbps
Source
Iran Intranet Access verified configs
First recorded check
2026-10-04 17:58:25 UTC
Recorded tunnel checks
11
Successful tunnel checks
10
Recorded tunnel success rate
90.9%

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.

Tunnel handshake (ms)
20570 10-04 17:5810-22 07:31Check time (UTC)
HTTPS first byte (ms)
93120 10-04 17:5810-22 07:31Check time (UTC)

Check history

Latest 11 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.

Recorded VMess checks, newest first
Checked (UTC)ResultHandshakeHTTPS first byteExit IP
Tunnel ok704 ms1,013 ms129.146.77.248
Tunnel ok719 ms1,031 ms129.146.77.248
Tunnel ok762 ms1,073 ms129.146.77.248
Tunnel ok1,659 ms1,976 ms129.146.77.248
Tunnel ok739 ms1,058 ms129.146.77.248
TimeoutNot measuredNot measuredNot verified
Tunnel ok828 ms1,167 ms129.146.77.248
Tunnel ok1,124 ms1,457 ms129.146.77.248
Tunnel ok724 ms1,068 ms129.146.77.248
Tunnel ok1,729 ms2,052 ms129.146.77.248
Tunnel ok2,057 ms9,312 ms129.146.77.248

How to use this VMess configuration

  1. Download the current configuration while a fresh verification is available.
  2. Import it into a VMess-compatible client, preserving all required transport, security and authentication parameters.
  3. 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.