Skip to main content
Tunnel verified at last checkLast result: 2026-10-23 18:44:27 UTC

Connection and verification

Protocol
Shadowsocks
Address
37.19.198.244:443
Transport / security
TCP / NONE
Last verified exit IP
37.19.198.244
Last verified handshake
349 ms
Last verified HTTPS first byte
522 ms
Download speed
2.854 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-04 13:42:54 UTC
Recorded tunnel checks
43
Successful tunnel checks
43
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)
4580 09-04 13:4210-23 18:44Check time (UTC)
HTTPS first byte (ms)
6270 09-04 13:4210-23 18:44Check time (UTC)

Check history

Latest 43 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 ok349 ms522 ms37.19.198.244
Tunnel ok380 ms553 ms37.19.198.244
Tunnel ok330 ms497 ms37.19.198.244
Tunnel ok338 ms513 ms37.19.198.244
Tunnel ok458 ms627 ms37.19.198.244
Tunnel ok398 ms610 ms37.19.198.244
Tunnel ok346 ms521 ms37.19.198.244
Tunnel ok347 ms527 ms37.19.198.244
Tunnel ok331 ms504 ms37.19.198.244
Tunnel ok327 ms493 ms37.19.198.244
Tunnel ok345 ms513 ms37.19.198.244
Tunnel ok347 ms558 ms37.19.198.244
Tunnel ok372 ms568 ms37.19.198.244
Tunnel ok385 ms551 ms37.19.198.244
Tunnel ok328 ms489 ms37.19.198.244
Tunnel ok320 ms484 ms37.19.198.244
Tunnel ok313 ms472 ms37.19.198.244
Tunnel ok335 ms504 ms37.19.198.244
Tunnel ok326 ms490 ms37.19.198.244
Tunnel ok372 ms540 ms37.19.198.244
Tunnel ok343 ms519 ms37.19.198.244
Tunnel ok343 ms513 ms37.19.198.244
Tunnel ok377 ms574 ms37.19.198.244
Tunnel ok334 ms519 ms37.19.198.244
Tunnel ok331 ms500 ms37.19.198.244
Tunnel ok353 ms530 ms37.19.198.244
Tunnel ok384 ms564 ms37.19.198.244
Tunnel ok399 ms572 ms37.19.198.244
Tunnel ok438 ms618 ms37.19.198.244
Tunnel ok356 ms535 ms37.19.198.244
Tunnel ok354 ms539 ms37.19.198.244
Tunnel ok345 ms527 ms37.19.198.244
Tunnel ok333 ms503 ms37.19.198.244
Tunnel ok356 ms539 ms37.19.198.244
Tunnel ok352 ms536 ms37.19.198.244
Tunnel ok355 ms535 ms37.19.198.244
Tunnel ok366 ms550 ms37.19.198.244
Tunnel ok374 ms574 ms37.19.198.244
Tunnel ok356 ms539 ms37.19.198.244
Tunnel ok384 ms574 ms37.19.198.244
Tunnel ok394 ms586 ms37.19.198.244
Tunnel ok390 ms583 ms37.19.198.244
Tunnel ok366 ms554 ms37.19.198.244

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.