Skip to main content
Tunnel verified at last checkLast result: 2026-10-08 13:23:03 UTC

Connection and verification

Protocol
Shadowsocks
Address
ce1fc2d8.krkt.hkssip.com:49642
Transport / security
TCP / NONE
Last verified exit IP
211.174.113.172
Last verified handshake
5,411 ms
Last verified HTTPS first byte
9,735 ms
Download speed
Not measured
Source
v2go hourly full-tunnel tested configs
First recorded check
2026-09-26 07:07:59 UTC
Recorded tunnel checks
11
Successful tunnel checks
11
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

Hover or focus a point for check details. Click or tap to keep them open.

Tunnel handshake (ms)
118770 09-28 14:3310-08 13:23Check time (UTC)
HTTPS first byte (ms)
179130 09-28 14:3310-08 13:23Check time (UTC)

Check history

Latest 12 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 Shadowsocks checks, newest first
Checked (UTC)ResultHandshakeHTTPS first byteExit IP
Tunnel ok5,411 ms9,735 ms211.174.113.172
Tunnel ok3,617 ms5,084 ms211.174.113.172
Tunnel ok5,519 ms9,547 ms211.174.113.172
Tunnel ok6,624 ms12,832 ms211.174.113.172
Tunnel ok5,150 ms9,528 ms211.174.113.172
Tunnel ok11,877 ms17,913 ms211.174.113.172
Tunnel ok2,541 ms3,999 ms211.174.113.172
Tunnel ok3,968 ms6,637 ms211.174.113.172
Tunnel ok3,240 ms4,644 ms211.174.113.172
Tunnel ok4,376 ms8,415 ms211.174.113.172
Tunnel ok1,045 ms1,559 ms211.174.113.172
Policy blockedNot measuredNot measuredNot verified

How to use this Shadowsocks configuration

  1. Download the current configuration while a fresh verification is available.
  2. Import it into a Shadowsocks-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 Shadowsocks 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 Shadowsocks guide, our checking methodology and public VPN risks.

This saved detail page remains available with its check history. Search indexing requires current successful full-tunnel verification, real measurements and an available configuration.