Skip to main content
Tunnel verified at last checkLast result: 2026-10-22 12:26:47 UTC

Connection and verification

Protocol
Shadowsocks
Address
82.38.31.34:8080
Transport / security
TCP / NONE
Last verified exit IP
193.29.139.199
Last verified handshake
228 ms
Last verified HTTPS first byte
423 ms
Download speed
6.78 Mbps
Source
v2go hourly full-tunnel tested configs
First recorded check
2026-09-09 02:02:34 UTC
Recorded tunnel checks
41
Successful tunnel checks
40
Recorded tunnel success rate
97.6%

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)
2820 09-11 01:4410-22 12:26Check time (UTC)
HTTPS first byte (ms)
5340 09-11 01:4410-22 12:26Check time (UTC)

Check history

Latest 42 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 ok228 ms423 ms193.29.139.199
Tunnel ok209 ms399 ms193.29.139.199
Tunnel ok219 ms406 ms193.29.139.199
Tunnel ok181 ms378 ms193.29.139.199
Tunnel ok180 ms351 ms193.29.139.199
Tunnel ok199 ms391 ms193.29.139.199
Tunnel ok231 ms429 ms193.29.139.199
Tunnel ok201 ms382 ms193.29.139.199
Tunnel ok203 ms383 ms193.29.139.199
Tunnel ok199 ms377 ms193.29.139.199
Tunnel ok195 ms367 ms193.29.139.199
Tunnel ok236 ms425 ms193.29.139.199
Tunnel ok189 ms361 ms193.29.139.199
Tunnel ok200 ms370 ms193.29.139.199
Tunnel ok171 ms334 ms193.29.139.199
Tunnel ok216 ms398 ms193.29.139.199
Tunnel ok175 ms348 ms193.29.139.199
Tunnel ok209 ms392 ms193.29.139.199
Tunnel ok205 ms385 ms193.29.139.199
Tunnel ok187 ms534 ms193.29.139.199
Tunnel ok228 ms422 ms193.29.139.199
Tunnel ok219 ms521 ms193.29.139.199
Tunnel ok203 ms377 ms193.29.139.199
Tunnel ok196 ms368 ms193.29.139.199
Tunnel ok220 ms419 ms193.29.139.199
Tunnel ok229 ms417 ms193.29.139.199
Tunnel ok216 ms402 ms193.29.139.199
Tunnel ok229 ms429 ms193.29.139.199
Tunnel ok282 ms500 ms193.29.139.199
Tunnel ok213 ms401 ms193.29.139.199
Tunnel ok224 ms419 ms193.29.139.199
Tunnel ok222 ms416 ms193.29.139.199
Tunnel ok211 ms400 ms193.29.139.199
Tunnel ok213 ms402 ms193.29.139.199
Tunnel ok200 ms388 ms193.29.139.199
Tunnel ok207 ms390 ms193.29.139.199
Tunnel ok227 ms418 ms193.29.139.199
Tunnel ok208 ms391 ms193.29.139.199
Tunnel ok227 ms409 ms193.29.139.199
Tunnel ok227 ms408 ms193.29.139.199
Tunnel failedNot 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.