Open proxy pool
1 901 live entries: HTTP, SOCKS5, SOCKS4. Anonymity, latency and uptime are measured with real connections — not pings. Output is published immediately.
The pool right now
Search index over address, network and country; sorted by 30-day uptime.
| # | Proxy | Protocol | Grade | Latency | Uptime 30d | Country |
|---|---|---|---|---|---|---|
| 1 | 63.180.203.233:8090 | HTTP | unknown | 89 ms | 100% | DE |
| 2 | 63.180.203.233:17410 | HTTP | unknown | 94 ms | 100% | DE |
| 3 | 56.228.13.15:13004 | HTTP | unknown | 103 ms | 100% | SE |
| 4 | 56.228.13.15:31196 | HTTP | unknown | 108 ms | 100% | SE |
| 5 | 56.228.13.15:6322 | HTTP | unknown | 110 ms | 100% | SE |
| 6 | 63.180.203.233:9595 | SOCKS5 | unknown | 112 ms | 100% | DE |
| 7 | 56.228.13.15:41965 | HTTP | unknown | 126 ms | 100% | SE |
| 8 | 18.170.45.5:4153 | HTTP | unknown | 129 ms | 100% | GB |
| 9 | 13.38.27.183:33033 | HTTP | unknown | 135 ms | 100% | FR |
| 10 | 18.170.45.5:37237 | HTTP | unknown | 135 ms | 100% | GB |
Output grades
elite does not reveal the client address or the fact of proxying; unknown — the proxy confirmed it is alive, but the level was not measured.
Queue verification cycle
196 of 202 sources responded in the latest cycle.
Sources and their contribution
Benchmark of external lists: how many addresses survive verification. Data comes alive only after a full pass.
| # | Source | Checked candidates | Alive | Live % | Median | Elite % | Published |
|---|---|---|---|---|---|---|---|
| 1 | thordata-socks5 | 22 | 20 | 90.9% | 1728.5 ms | 10% | 33 |
| 2 | stormsia-working | 57 | 46 | 80.7% | 1513 ms | 19.6% | 150 |
| 3 | zloi-user-socks5 | 54 | 42 | 77.8% | 3172 ms | 21.4% | 338 |
| 4 | stormsia-socks5 | 26 | 20 | 76.9% | 1517 ms | 20% | 50 |
| 5 | hproxy-socks5 | 173 | 130 | 75.1% | 1548 ms | 13.8% | 1 534 |
| 6 | maximilianfeix-socks5 | 59 | 44 | 74.6% | 2010 ms | 13.6% | 360 |
| 7 | zaeem20-socks5 | 59 | 44 | 74.6% | 1236 ms | 15.9% | 285 |
| 8 | health-list-socks5 | 156 | 113 | 72.4% | 1639 ms | 9.7% | 668 |
top 8 of 202 sources · updated with each run · full benchmark
Files and API
The output is published in full, including nodes that did not make it into the demo page sorting.
Treat every entry as hostile: a public proxy can intercept and alter traffic. Do not send accounts, passwords or private data through it.
A catalog, not an operator
The connection is established directly between the client and the node. We publish verified addresses from open lists and do not participate in traffic transmission.
what the pool should not be used for
The node operator is responsible for actions on the nodes. For sensitive data, use the platform VPN configurations.
VPN — configurations with full verification