Skip to main content
Tunnel verified at last checkLast result: 2026-09-12 03:20:26 UTC

Connection and verification

Protocol
Shadowsocks
Address
37.19.198.236:443
Transport / security
TCP / NONE
Last verified exit IP
37.19.198.236
Last verified handshake
371 ms
Last verified HTTPS first byte
558 ms
Download speed
4.239 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-04 13:26:04 UTC
Recorded tunnel checks
5
Successful tunnel checks
5
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)
4080 2026-09-04 13:26:04 UTC: 377 ms2026-09-07 17:33:29 UTC: 375 ms2026-09-09 20:30:44 UTC: 408 ms2026-09-11 04:13:45 UTC: 362 ms2026-09-12 03:20:26 UTC: 371 ms09-04 13:2609-12 03:20Check time (UTC)
HTTPS first byte (ms)
6160 2026-09-04 13:26:04 UTC: 564 ms2026-09-07 17:33:29 UTC: 572 ms2026-09-09 20:30:44 UTC: 616 ms2026-09-11 04:13:45 UTC: 546 ms2026-09-12 03:20:26 UTC: 558 ms09-04 13:2609-12 03:20Check time (UTC)

Check history

Latest 5 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 ok371 ms558 ms37.19.198.236
Tunnel ok362 ms546 ms37.19.198.236
Tunnel ok408 ms616 ms37.19.198.236
Tunnel ok375 ms572 ms37.19.198.236
Tunnel ok377 ms564 ms37.19.198.236

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.