Shadowsocks server 37.19.198.236:443
TCP / NONE · Firmfox Proxify mixed configs
Inactive — did not pass verificationLast result: 2026-10-22 07:17:52 UTC
This endpoint has no current downloadable verification, or a newer check did not succeed. Previous measurements below are historical. Choose another checked Shadowsocks server.
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
- 434 ms
- Last verified HTTPS first byte
- 602 ms
- Download speed
- 3.713 Mbps
- Source
- Firmfox Proxify mixed configs
- First recorded check
- 2026-09-05 12:00:04 UTC
- Recorded tunnel checks
- 35
- Successful tunnel checks
- 35
- 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.
Check history
Latest 35 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.
| Checked (UTC) | Result | Handshake | HTTPS first byte | Exit IP |
|---|---|---|---|---|
| Tunnel ok | 434 ms | 602 ms | 37.19.198.236 | |
| Tunnel ok | 346 ms | 525 ms | 37.19.198.236 | |
| Tunnel ok | 431 ms | 632 ms | 37.19.198.236 | |
| Tunnel ok | 334 ms | 504 ms | 37.19.198.236 | |
| Tunnel ok | 384 ms | 584 ms | 37.19.198.236 | |
| Tunnel ok | 346 ms | 520 ms | 37.19.198.236 | |
| Tunnel ok | 337 ms | 517 ms | 37.19.198.236 | |
| Tunnel ok | 330 ms | 533 ms | 37.19.198.236 | |
| Tunnel ok | 329 ms | 497 ms | 37.19.198.236 | |
| Tunnel ok | 377 ms | 549 ms | 37.19.198.236 | |
| Tunnel ok | 347 ms | 520 ms | 37.19.198.236 | |
| Tunnel ok | 327 ms | 493 ms | 37.19.198.236 | |
| Tunnel ok | 323 ms | 489 ms | 37.19.198.236 | |
| Tunnel ok | 334 ms | 507 ms | 37.19.198.236 | |
| Tunnel ok | 316 ms | 474 ms | 37.19.198.236 | |
| Tunnel ok | 525 ms | 763 ms | 37.19.198.236 | |
| Tunnel ok | 331 ms | 505 ms | 37.19.198.236 | |
| Tunnel ok | 343 ms | 517 ms | 37.19.198.236 | |
| Tunnel ok | 331 ms | 501 ms | 37.19.198.236 | |
| Tunnel ok | 333 ms | 502 ms | 37.19.198.236 | |
| Tunnel ok | 371 ms | 560 ms | 37.19.198.236 | |
| Tunnel ok | 347 ms | 521 ms | 37.19.198.236 | |
| Tunnel ok | 333 ms | 506 ms | 37.19.198.236 | |
| Tunnel ok | 389 ms | 575 ms | 37.19.198.236 | |
| Tunnel ok | 374 ms | 563 ms | 37.19.198.236 | |
| Tunnel ok | 359 ms | 544 ms | 37.19.198.236 | |
| Tunnel ok | 594 ms | 1,015 ms | 37.19.198.236 | |
| Tunnel ok | 370 ms | 573 ms | 37.19.198.236 | |
| Tunnel ok | 359 ms | 555 ms | 37.19.198.236 | |
| Tunnel ok | 371 ms | 567 ms | 37.19.198.236 | |
| Tunnel ok | 361 ms | 541 ms | 37.19.198.236 | |
| Tunnel ok | 362 ms | 536 ms | 37.19.198.236 | |
| Tunnel ok | 403 ms | 621 ms | 37.19.198.236 | |
| Tunnel ok | 375 ms | 571 ms | 37.19.198.236 | |
| Tunnel ok | 462 ms | 706 ms | 37.19.198.236 |
No recorded checks match this filter.
How to use this Shadowsocks configuration
- Download the current configuration while a fresh verification is available.
- Import it into a Shadowsocks-compatible client, preserving all required transport, security and authentication parameters.
- 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.
This saved detail page remains available with its check history. Search indexing requires current successful full-tunnel verification, real measurements and an available configuration.