VLESS server 148.113.5.44:443
TCP / REALITY · Iran Intranet Access verified configs
Tunnel verified at last checkLast result: 2026-10-09 03:45:01 UTC
Connection and verification
- Protocol
- VLESS
- Address
- 148.113.5.44:443
- Transport / security
- TCP / REALITY
- Last verified exit IP
- 148.113.5.44
- Last verified handshake
- 1,073 ms
- Last verified HTTPS first byte
- 1,760 ms
- Download speed
- 2.373 Mbps
- Source
- Iran Intranet Access verified configs
- First recorded check
- 2026-09-14 09:32:02 UTC
- Recorded tunnel checks
- 26
- Successful tunnel checks
- 22
- Recorded tunnel success rate
- 84.6%
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 26 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,073 ms | 1,760 ms | 148.113.5.44 | |
| Tunnel ok | 10,108 ms | 10,591 ms | 148.113.5.44 | |
| Tunnel ok | 6,395 ms | 6,869 ms | 148.113.5.44 | |
| Tunnel ok | 792 ms | 1,266 ms | 148.113.5.44 | |
| Tunnel ok | 828 ms | 1,508 ms | 148.113.5.44 | |
| Timeout | Not measured | Not measured | Not verified | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 5,078 ms | 5,547 ms | 148.113.5.44 | |
| Tunnel ok | 1,808 ms | 2,262 ms | 148.113.5.44 | |
| Tunnel ok | 809 ms | 1,260 ms | 148.113.5.44 | |
| Tunnel ok | 816 ms | 1,296 ms | 148.113.5.44 | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 1,177 ms | 1,847 ms | 148.113.5.44 | |
| Tunnel ok | 3,864 ms | 4,320 ms | 148.113.5.44 | |
| Tunnel ok | 3,836 ms | 4,284 ms | 148.113.5.44 | |
| Tunnel ok | 1,037 ms | 2,005 ms | 148.113.5.44 | |
| Tunnel ok | 842 ms | 1,365 ms | 148.113.5.44 | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel ok | 874 ms | 1,373 ms | 148.113.5.44 | |
| Tunnel ok | 824 ms | 1,304 ms | 148.113.5.44 | |
| Tunnel ok | 831 ms | 1,294 ms | 148.113.5.44 | |
| Tunnel ok | 1,054 ms | 1,534 ms | 148.113.5.44 | |
| Tunnel ok | 832 ms | 1,318 ms | 148.113.5.44 | |
| Tunnel ok | 813 ms | 1,318 ms | 148.113.5.44 | |
| Tunnel ok | 853 ms | 1,329 ms | 148.113.5.44 | |
| Tunnel ok | 872 ms | 1,360 ms | 148.113.5.44 |
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.
This saved detail page remains available with its check history. Search indexing requires current successful full-tunnel verification, real measurements and an available configuration.