Skip to main content
Inactive — did not pass verificationLast result: 2026-09-11 08:08:00 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
oc.imfun.fun:18112
Transport / security
TCP / NONE
Last verified exit IP
168.110.60.104
Last verified handshake
2,317 ms
Last verified HTTPS first byte
2,877 ms
Download speed
2.767 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-05 09:38:48 UTC
Recorded tunnel checks
5
Successful tunnel checks
3
Recorded tunnel success rate
60.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

Tunnel handshake (ms)
23890 2026-09-05 09:38:48 UTC: 2,389 ms2026-09-08 17:54:59 UTC: 2,248 ms2026-09-09 23:17:10 UTC: 2,317 ms09-05 09:3809-09 23:17Check time (UTC)
HTTPS first byte (ms)
29140 2026-09-05 09:38:48 UTC: 2,914 ms2026-09-08 17:54:59 UTC: 2,758 ms2026-09-09 23:17:10 UTC: 2,877 ms09-05 09:3809-09 23:17Check time (UTC)

Check history

Latest 5 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
TimeoutNot measuredNot measuredNot verified
Tunnel ok2,317 ms2,877 ms168.110.60.104
Tunnel ok2,248 ms2,758 ms168.110.60.104
TimeoutNot measuredNot measuredNot verified
Tunnel ok2,389 ms2,914 ms168.110.60.104

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.