Skip to main content
Inactive — did not pass verificationLast result: 2026-09-12 02:06:13 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
qtkdr8jxe3wefxjm.v.3dns.vip:443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
8.217.229.155
Last verified handshake
4,348 ms
Last verified HTTPS first byte
4,872 ms
Download speed
Not measured
Source
v2go hourly full-tunnel tested configs
First recorded check
2026-09-08 20:21:21 UTC
Recorded tunnel checks
3
Successful tunnel checks
2
Recorded tunnel success rate
66.7%

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)
63040 2026-09-11 03:05:29 UTC: 6,304 ms2026-09-12 02:06:13 UTC: 4,348 ms09-11 03:0509-12 02:06Check time (UTC)
HTTPS first byte (ms)
70360 2026-09-11 03:05:29 UTC: 7,036 ms2026-09-12 02:06:13 UTC: 4,872 ms09-11 03:0509-12 02:06Check 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 ok4,348 ms4,872 ms8.217.229.155
Tunnel ok6,304 ms7,036 ms8.217.229.155
Tunnel failedNot measuredNot measuredNot verified
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.