Skip to main content
Tunnel verified at last checkLast result: 2026-09-11 13:00:41 UTC

Connection and verification

Protocol
Shadowsocks
Address
82.38.31.149:8080
Transport / security
TCP / NONE
Last verified exit IP
193.29.139.195
Last verified handshake
242 ms
Last verified HTTPS first byte
613 ms
Download speed
6.855 Mbps
Source
v2go hourly full-tunnel tested configs
First recorded check
2026-09-07 10:03:11 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)
2420 2026-09-10 02:14:39 UTC: 198 ms2026-09-11 13:00:41 UTC: 242 ms09-10 02:1409-11 13:00Check time (UTC)
HTTPS first byte (ms)
6130 2026-09-10 02:14:39 UTC: 380 ms2026-09-11 13:00:41 UTC: 613 ms09-10 02:1409-11 13:00Check time (UTC)

Check history

Latest 3 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 ok242 ms613 ms193.29.139.195
Tunnel ok198 ms380 ms193.29.139.195
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.