Skip to main content
Inactive — did not pass verificationLast result: 2026-09-11 22:43:14 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
168.110.60.104:18112
Transport / security
TCP / NONE
Last verified exit IP
168.110.60.104
Last verified handshake
713 ms
Last verified HTTPS first byte
1,221 ms
Download speed
2.84 Mbps
Source
v2go hourly full-tunnel tested configs
First recorded check
2026-09-09 10:55:13 UTC
Recorded tunnel checks
3
Successful tunnel checks
3
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

Tunnel handshake (ms)
7130 2026-09-09 19:06:02 UTC: 691 ms2026-09-10 23:42:25 UTC: 712 ms2026-09-11 22:43:14 UTC: 713 ms09-09 19:0609-11 22:43Check time (UTC)
HTTPS first byte (ms)
12280 2026-09-09 19:06:02 UTC: 1,190 ms2026-09-10 23:42:25 UTC: 1,228 ms2026-09-11 22:43:14 UTC: 1,221 ms09-09 19:0609-11 22:43Check time (UTC)

Check history

Latest 4 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 ok713 ms1,221 ms168.110.60.104
Tunnel ok712 ms1,228 ms168.110.60.104
Tunnel ok691 ms1,190 ms168.110.60.104
Policy blockedNot measuredNot measuredNot verified

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.