Skip to main content
Tunnel verified at last checkLast result: 2026-10-08 23:36:08 UTC

Connection and verification

Protocol
VLESS
Address
108.61.164.217:4443
Transport / security
TCP / REALITY
Last verified exit IP
108.61.164.217
Last verified handshake
312 ms
Last verified HTTPS first byte
493 ms
Download speed
2.32 Mbps
Source
Iran Intranet Access verified configs
First recorded check
2026-09-28 10:26:13 UTC
Recorded tunnel checks
12
Successful tunnel checks
12
Recorded tunnel success rate
100.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.

Tunnel handshake (ms)
4770 09-28 10:2610-08 23:36Check time (UTC)
HTTPS first byte (ms)
6960 09-28 10:2610-08 23:36Check time (UTC)

Check history

Latest 12 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 VLESS checks, newest first
Checked (UTC)ResultHandshakeHTTPS first byteExit IP
Tunnel ok312 ms493 ms108.61.164.217
Tunnel ok477 ms696 ms108.61.164.217
Tunnel ok293 ms472 ms108.61.164.217
Tunnel ok337 ms519 ms108.61.164.217
Tunnel ok321 ms512 ms108.61.164.217
Tunnel ok367 ms560 ms108.61.164.217
Tunnel ok292 ms465 ms108.61.164.217
Tunnel ok346 ms533 ms108.61.164.217
Tunnel ok342 ms533 ms108.61.164.217
Tunnel ok383 ms591 ms108.61.164.217
Tunnel ok358 ms561 ms108.61.164.217
Tunnel ok361 ms573 ms108.61.164.217

How to use this VLESS configuration

  1. Download the current configuration while a fresh verification is available.
  2. Import it into a VLESS-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 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.

This saved detail page remains available with its check history. Search indexing requires current successful full-tunnel verification, real measurements and an available configuration.