Skip to main content
Inactive — did not pass verificationLast result: 2026-09-11 14:16: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
155.248.176.44:55216
Transport / security
TCP / NONE
Last verified exit IP
155.248.176.44
Last verified handshake
686 ms
Last verified HTTPS first byte
1,210 ms
Download speed
2.403 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-05 12:45:52 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)
6860 2026-09-05 12:45:52 UTC: 667 ms2026-09-11 14:16:00 UTC: 686 ms09-05 12:4509-11 14:16Check time (UTC)
HTTPS first byte (ms)
12100 2026-09-05 12:45:52 UTC: 1,177 ms2026-09-11 14:16:00 UTC: 1,210 ms09-05 12:4509-11 14:16Check 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
Tunnel ok686 ms1,210 ms155.248.176.44
Unsupported checkerNot measuredNot measuredNot verified
Unsupported checkerNot measuredNot measuredNot verified
Unsupported checkerNot measuredNot measuredNot verified
Tunnel ok667 ms1,177 ms155.248.176.44

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.