VMess server jp4.998998.best:443

Connection and verification

Protocol

VMess

Address

jp4.998998.best:443

Transport / security

WEBSOCKET / TLS

Last verified exit IP

152.70.250.217

Last verified handshake

8,220 ms

Last verified HTTPS first byte

8,771 ms

Download speed

Not measured

Source

v2go hourly full-tunnel tested configs

First recorded check

2026-10-11 11:22:53 UTC

Recorded tunnel checks

10

Successful tunnel checks

1

Recorded tunnel success rate

10.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

At least two recorded measurements are needed for a chart. Earlier VMess checks were stored as the latest result only; new results now accumulate automatically.

Check history

Latest 10 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.

No recorded checks match this filter.

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.