Skip to main content
Tunnel verified at last checkLast result: 2026-10-23 21:31:10 UTC

Connection and verification

Protocol
Shadowsocks
Address
216.105.168.18:443
Transport / security
TCP / NONE
Last verified exit IP
216.105.168.18
Last verified handshake
6,011 ms
Last verified HTTPS first byte
6,318 ms
Download speed
1.239 Mbps
Source
v2go hourly full-tunnel tested configs
First recorded check
2026-09-07 00:53:55 UTC
Recorded tunnel checks
38
Successful tunnel checks
33
Recorded tunnel success rate
86.8%

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)
104840 09-11 21:0910-23 21:31Check time (UTC)
HTTPS first byte (ms)
107930 09-11 21:0910-23 21:31Check time (UTC)

Check history

Latest 40 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 ok6,011 ms6,318 ms216.105.168.18
Tunnel ok508 ms822 ms216.105.168.18
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok514 ms828 ms216.105.168.18
Tunnel ok10,484 ms10,793 ms216.105.168.18
Tunnel ok621 ms920 ms216.105.168.18
Tunnel ok549 ms861 ms216.105.168.18
Tunnel ok541 ms889 ms216.105.168.18
Tunnel ok524 ms858 ms216.105.168.18
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok1,905 ms2,266 ms216.105.168.18
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok514 ms842 ms216.105.168.18
Tunnel ok6,308 ms6,629 ms216.105.168.18
Tunnel ok5,781 ms6,098 ms216.105.168.18
Tunnel ok475 ms773 ms216.105.168.18
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok504 ms804 ms216.105.168.18
Tunnel ok493 ms813 ms216.105.168.18
Tunnel ok1,042 ms1,351 ms216.105.168.18
Tunnel ok530 ms858 ms216.105.168.18
Tunnel ok527 ms852 ms216.105.168.18
Tunnel ok528 ms854 ms216.105.168.18
Tunnel ok504 ms832 ms216.105.168.18
Tunnel ok523 ms846 ms216.105.168.18
Tunnel ok555 ms899 ms216.105.168.18
Tunnel ok592 ms966 ms216.105.168.18
Tunnel ok645 ms1,013 ms216.105.168.18
Tunnel ok538 ms884 ms216.105.168.18
Tunnel ok5,503 ms5,827 ms216.105.168.18
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok609 ms966 ms216.105.168.18
Tunnel ok1,474 ms1,814 ms216.105.168.18
Tunnel ok549 ms886 ms216.105.168.18
Tunnel ok3,550 ms3,858 ms216.105.168.18
Tunnel ok543 ms863 ms216.105.168.18
Tunnel ok2,141 ms2,464 ms216.105.168.18
Tunnel ok521 ms854 ms216.105.168.18
Policy blockedNot measuredNot measuredNot verified
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.