Scanned and filtered down to what actually answered. Response time is measured from Frankfurt, so treat it as a rough sort rather than a promise. Expect roughly half of these to stop answering by tomorrow.
| IP : port | Country | Type | Response | Uptime |
|---|---|---|---|---|
| 134.209.29.120:1080 | United Kingdom | SOCKS5 | 0.13 s | 70% |
| 185.73.115.109:2080 | The Netherlands | SOCKS5 | 0.39 s | 87% |
| 209.97.150.167:1080 | United States | SOCKS5 | 0.40 s | 68% |
| 198.199.86.11:1080 | United States | SOCKS5 | 0.59 s | 67% |
| 107.174.30.92:1080 | United States | SOCKS5 | 0.87 s | 67% |
| 192.111.139.162:4145 | United States | SOCKS5 | 0.92 s | 82% |
| 192.252.211.193:4145 | United States | SOCKS5 | 0.92 s | 86% |
| 74.119.144.60:4145 | United States | SOCKS5 | 0.93 s | 90% |
| 184.170.248.5:4145 | United States | SOCKS5 | 0.94 s | 89% |
| 67.201.59.70:4145 | United States | SOCKS5 | 0.94 s | 70% |
| 192.252.208.70:14282 | United States | SOCKS5 | 0.94 s | 66% |
| 199.102.107.145:4145 | United States | SOCKS5 | 0.96 s | 75% |
| 192.111.139.163:19404 | United States | SOCKS5 | 0.96 s | 62% |
| 198.8.84.3:4145 | United States | SOCKS5 | 0.99 s | 80% |
| 192.111.137.35:4145 | United States | SOCKS5 | 0.99 s | 67% |
| 184.178.172.5:15303 | United States | SOCKS5 | 1.00 s | 62% |
| 195.19.50.85:1080 | Russia | SOCKS5 | 1.00 s | 85% |
| 184.178.172.18:15280 | United States | SOCKS5 | 1.00 s | 84% |
| 98.170.57.249:4145 | United States | SOCKS5 | 1.01 s | 77% |
| 72.195.114.169:4145 | United States | SOCKS5 | 1.02 s | 77% |
| 98.170.57.241:4145 | United States | SOCKS5 | 1.06 s | 88% |
| 124.41.225.101:1080 | Nepal | SOCKS5 | 1.13 s | 65% |
| 66.42.224.229:41679 | United States | SOCKS5 | 1.13 s | 79% |
| 104.37.135.145:4145 | United States | SOCKS5 | 1.42 s | 89% |
| 81.0.49.104:18500 | Spain | SOCKS5 | 1.47 s | 89% |
| 176.37.107.86:11111 | Ukraine | SOCKS5 | 1.48 s | 85% |
| 166.62.35.102:45775 | United States | SOCKS5 | 1.58 s | 91% |
| 111.119.162.248:10935 | Pakistan | SOCKS5 | 1.59 s | 71% |
| 42.112.52.16:20001 | Vietnam | SOCKS5 | 1.65 s | 62% |
| 116.101.14.169:1080 | Vietnam | SOCKS5 | 1.68 s | 64% |
| 80.79.241.118:1080 | Russia | SOCKS5 | 1.72 s | 74% |
| 143.198.239.45:10025 | United States | SOCKS5 | 1.76 s | 85% |
| 3.229.156.137:6000 | United States | SOCKS5 | 1.78 s | 63% |
| 36.155.23.163:10808 | China | SOCKS5 | 1.99 s | 80% |
| 183.172.126.63:10808 | China | SOCKS5 | 2.40 s | 97% |
| 185.73.115.43:2080 | The Netherlands | SOCKS5 | 2.49 s | 70% |
| 153.80.242.105:8080 | Germany | SOCKS5 | 2.57 s | 63% |
| 195.13.182.212:8888 | Latvia | SOCKS5 | 2.57 s | 77% |
| 194.87.191.118:20090 | The Netherlands | SOCKS5 | 2.66 s | 80% |
| 38.79.114.43:8885 | United States | SOCKS5 | 3.03 s | 61% |
| 193.43.104.206:1080 | Germany | SOCKS5 | 3.44 s | 77% |
| 160.22.200.60:69 | Indonesia | SOCKS5 | 3.45 s | 74% |
| 202.62.50.52:1080 | Cambodia | SOCKS5 | 3.49 s | 78% |
| 5.75.133.113:10808 | Germany | SOCKS5 | 3.71 s | 73% |
| 158.94.173.13:1080 | United States | SOCKS5 | 3.90 s | 96% |
| 202.142.153.220:1080 | Pakistan | SOCKS5 | 4.00 s | 63% |
| 118.179.144.113:9090 | Bangladesh | SOCKS5 | 4.30 s | 87% |
| 217.165.51.161:10800 | United Arab Emirates | SOCKS5 | 4.31 s | 69% |
| 103.180.123.111:1080 | Indonesia | SOCKS5 | 4.74 s | 79% |
| 103.138.145.204:1999 | Bangladesh | SOCKS5 | 4.86 s | 67% |
| 95.170.122.80:2080 | Russia | SOCKS5 | 4.94 s | 68% |
| 65.21.252.66:10813 | Finland | SOCKS5 | 5.14 s | 61% |
| 202.4.123.220:9090 | Bangladesh | SOCKS5 | 5.44 s | 78% |
| 176.126.70.111:16379 | Sweden | SOCKS5 | 5.56 s | 90% |
| 109.95.175.64:1080 | Poland | SOCKS5 | 5.69 s | 71% |
| 85.142.124.27:1080 | Russia | SOCKS5 | 6.38 s | 93% |
| 145.255.20.211:1080 | Russia | SOCKS5 | 7.04 s | 93% |
| 172.247.27.29:11080 | United States | SOCKS5 | 7.43 s | 84% |
Response is a single connect from Frankfurt. Under a second is comfortable, up to two seconds is usable, past that you feel it on every request.
Uptime is how often this address answered across recent checks. Under 60 per cent means it is already dying; take the top of the table first.
None of these belong on an account you care about. They are shared, they are logged by whoever left them open, and they change hands without warning. For anything tied to a login, an address from an IP from a phone operator behaves like a normal subscriber and does not carry the history of a public list.
Everything published since 2011 sits in the month archive. If you need addresses that hold for months rather than hours, they are for sale as a proxy pool for rank checks.