Skip to main content
Inactive — did not pass verificationLast result: 2026-09-07 22:11:34 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
129.146.77.248:39495
Transport / security
WEBSOCKET / NONE
Last verified exit IP
129.146.77.248
Last verified handshake
793 ms
Last verified HTTPS first byte
1,136 ms
Download speed
Not measured
Source
Barry VMess
First recorded check
2026-09-04 13:59:00 UTC
Recorded tunnel checks
2
Successful tunnel checks
2
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)
9110 2026-09-04 13:59:00 UTC: 911 ms2026-09-07 22:11:34 UTC: 793 ms09-04 13:5909-07 22:11Check time (UTC)
HTTPS first byte (ms)
12470 2026-09-04 13:59:00 UTC: 1,247 ms2026-09-07 22:11:34 UTC: 1,136 ms09-04 13:5909-07 22:11Check time (UTC)

Check history

Latest 2 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 ok793 ms1,136 ms129.146.77.248
Tunnel ok911 ms1,247 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.