HProxy · Free Russia SOCKS4 pool

RUFree Russia SOCKS4 proxy list 2026

Every proxy below speaks SOCKS4 from an address in Russia, re-checked on a rolling cycle. The numbers on this page come from our own checker, measured on 15 September 2026.

RURussiaElite
46.8.221.144:10808
100%715 ms
HTTPASKONTEL
RURussiaElite
5.42.111.165:10808
85%2687 ms
HTTPTimeWeb-AS
RURussiaElite
46.0.176.126:10808
60%1987 ms
HTTPESAMARA-AS
RURussiaElite
83.219.1.130:5678
43%2166 ms
SOCKS4PJSC "Rostelecom". Technical Team
RURussiaElite
46.17.43.219:7890
43%18696 ms
HTTPASBAXET
RURussiaElite
85.15.190.8:10808
38%4579 ms
HTTPPJSC "Rostelecom". Technical Team
RURussiaElite
85.237.62.189:3629
35%1221 ms
SOCKS4PJSC "Rostelecom". Technical Team
RURussiaElite
95.80.89.38:1080
35%3350 ms
SOCKS4QUANTUM
RURussiaElite
46.8.104.176:1080
33%1088 ms
SOCKS4ET-AS
RURussiaElite
37.193.125.68:1090
33%6111 ms
SOCKS4IPv6 customers
RURussiaElite
91.223.224.238:48293
31%1278 ms
SOCKS4ATK-Telecom
RURussiaElite
109.232.106.150:52435
31%2134 ms
SOCKS4TYFON-AS
RURussiaAnonymous
178.69.224.60:10808
31%2949 ms
HTTPPJSC "Rostelecom". Technical Team
RURussiaElite
94.247.241.70:51006
31%3992 ms
SOCKS4ZTELECOM-AS
RURussiaElite
88.87.79.18:3629
29%4902 ms
SOCKS4EVOLGOGRAD-AS
RURussiaElite
185.216.18.138:44550
27%2820 ms
SOCKS4MEGATEC-AS
RURussiaElite
176.192.41.172:4444
27%2904 ms
SOCKS4Moscow, Russia
RURussiaElite
45.90.217.190:1085
27%6109 ms
SOCKS4FIRST-SERVER-EUROPE
RURussiaElite
217.17.112.98:1080
26%927 ms
SOCKS4OOO_KISS
RURussiaElite
109.230.129.20:10808
26%1512 ms
HTTPVSEVNET-AS
RURussiaElite
95.46.105.163:4145
26%3459 ms
SOCKS4KOMPLEKS-MEDIA-AS
RURussiaElite
213.87.101.134:1080
25%4945 ms
SOCKS4MTS
RURussiaElite
89.151.134.157:3629
24%2963 ms
SOCKS4PJSC "Rostelecom". Technical Team
RURussiaElite
212.220.13.98:4153
23%2721 ms
SOCKS4PJSC "Rostelecom". Technical Team
RURussiaElite
83.220.46.106:4145
23%4412 ms
SOCKS4Moscow, Russia
RURussiaElite
109.68.189.22:54643
23%5981 ms
SOCKS4TEL-NET-AS
RURussiaElite
37.193.71.189:1080
22%1570 ms
SOCKS4IPv6 customers
RURussiaElite
46.8.60.34:1080
22%1577 ms
SOCKS4AVANTA-AS
RURussiaElite
31.148.13.96:1080
22%2431 ms
SOCKS4-- RT --
RURussiaElite
147.45.249.29:1080
22%3027 ms
SOCKS4TimeWeb-AS
RURussiaElite
89.191.229.141:1080
22%8540 ms
SOCKS4TimeWeb-AS
RURussiaElite
85.113.204.41:8080
21%1031 ms
SOCKS4PJSC "Rostelecom". Yaroslavl branch
RURussiaElite
94.253.95.241:3629
21%1116 ms
SOCKS4ITKM-AS
RURussiaElite
176.214.78.230:5678
21%1596 ms
SOCKS4YAR-AS
RURussiaElite
92.255.190.64:4153
21%1922 ms
SOCKS4ERTH-OMSK-AS
RURussiaElite
95.188.83.253:1080
21%2371 ms
SOCKS4PJSC "Rostelecom". Technical Team
RURussiaElite
188.93.64.242:4153
21%5240 ms
SOCKS4ASTIMER
RURussiaElite
194.67.207.95:19080
21%5406 ms
SOCKS4I-SERVERS-EAST
RURussiaElite
195.133.197.14:1080
21%8332 ms
SOCKS4MTW-AS
RURussiaElite
5.23.104.251:1080
20%2157 ms
SOCKS4VIDIKON
RURussiaElite
89.250.148.154:4145
20%3022 ms
SOCKS4ERTH-TMN-AS
RURussiaElite
89.250.148.158:1080
20%5620 ms
SOCKS4ERTH-TMN-AS
RURussiaElite
90.188.92.116:36335
20%8606 ms
SOCKS4PJSC "Rostelecom". Technical Team
RURussiaElite
213.21.53.119:4153
19%1029 ms
SOCKS4-------------- eTelecom Customers (localpref 500) --------------
RURussiaElite
185.26.168.17:4153
19%3659 ms
SOCKS4DELTATELEKOM-AS
RURussiaElite
109.106.196.250:4145
19%4609 ms
SOCKS4PJSC MegaFon
RURussiaElite
92.100.221.184:9050
19%5393 ms
SOCKS4PJSC "Rostelecom". Technical Team
RURussiaElite
188.143.169.22:33333
19%5486 ms
SOCKS4PIN-AS
RURussiaElite
31.220.163.133:1080
19%62821 ms
SOCKS4RDTC Autonomous System ISP at Novokuznetsk city
RURussiaElite
178.57.106.43:4145
18%903 ms
SOCKS4Sever-Telecom-Cher
RURussiaElite
46.188.2.42:5678
18%1227 ms
SOCKS4Moscow
RURussiaElite
176.118.232.12:5678
18%2095 ms
SOCKS4ASTIMER
RURussiaElite
5.254.178.160:10801
18%2161 ms
SOCKS4Retail
RURussiaElite
213.210.67.186:3629
18%2370 ms
SOCKS4OJSC "Tomsktelecom"
RURussiaElite
212.103.118.77:5678
18%2617 ms
SOCKS4BRYANSK-AS
RURussiaElite
85.30.215.48:60541
18%6771 ms
SOCKS4OJSC "National Cable Networks"
RURussiaElite
46.29.116.3:4145
18%8410 ms
SOCKS4POTOK-AS
RURussiaElite
51.250.6.232:1080
18%8920 ms
SOCKS4YandexCloud
RURussiaElite
212.46.242.185:1080
17%4933 ms
SOCKS4SOVAM-AS
RURussiaElite
92.42.8.5:4145
17%5364 ms
SOCKS4POTOK-AS
RURussiaElite
46.29.116.6:4145
17%7944 ms
SOCKS4POTOK-AS
RURussiaElite
92.42.8.20:4145
16%1834 ms
SOCKS4POTOK-AS
RURussiaElite
213.248.39.166:4153
15%2645 ms
SOCKS4DINET-AS
RURussiaElite
95.163.20.1:4153
15%4047 ms
SOCKS4DINET-AS
RURussiaElite
93.100.133.197:1080
15%4439 ms
SOCKS4<Sky>
RURussiaElite
185.30.43.65:60606
14%7560 ms
SOCKS4SERDI-AS
RURussiaElite
37.195.116.105:1080
14%9628 ms
SOCKS4IPv6 customers
RURussiaElite
185.135.81.149:9060
13%2383 ms
SOCKS4ADMAN-AS
RURussiaElite
109.197.55.234:1080
13%2961 ms
SOCKS4KOLPINONET-AS
RURussiaElite
89.237.32.193:51549
13%5800 ms
SOCKS4Moscow, Russia
RURussiaElite
141.98.188.251:9050
13%20358 ms
SOCKS4UFO-AS
RURussiaElite
91.210.151.184:1080
12%2262 ms
SOCKS4SKYINET-AS
RURussiaElite
195.46.172.190:4153
12%6369 ms
SOCKS4SOVAM-AS
RURussiaElite
213.171.26.67:8008
12%10518 ms
SOCKS4CLOUDRU-AS
RURussiaElite
91.246.1.6:4433
12%16362 ms
SOCKS4BAIKAL-TELEPORT-AS
RURussiaElite
31.163.200.63:4153
11%1857 ms
SOCKS4PJSC "Rostelecom". Technical Team
RURussiaElite
195.68.145.5:80
11%2827 ms
SOCKS4SOVAM-AS
RURussiaElite
51.250.22.208:10808
11%3148 ms
HTTPYandexCloud
RURussiaElite
89.237.32.161:51549
11%5269 ms
SOCKS4Moscow, Russia
RURussiaElite
77.95.201.16:9150
11%6045 ms
SOCKS4TimeWeb-AS
RURussiaElite
5.188.78.218:9150
11%6935 ms
SOCKS4SELECTEL-MSK
RURussiaElite
31.130.132.156:9050
11%7843 ms
SOCKS4ADMAN-AS
RURussiaElite
109.201.65.228:1080
10%1449 ms
SOCKS4LLC-ZHANR-AS
RURussiaElite
92.39.69.134:11200
10%1537 ms
SOCKS4MTS
RURussiaElite
92.42.8.22:4153
10%2008 ms
SOCKS4POTOK-AS
RURussiaElite
5.166.12.63:5555
10%2319 ms
SOCKS4YAR-AS
RURussiaElite
213.87.10.138:10808
10%5701 ms
HTTPSMTS
RURussiaElite
91.206.92.212:9050
10%6015 ms
SOCKS4ASBAXET
RURussiaElite
93.90.212.2:4153
9%1368 ms
SOCKS4POTOK-AS
RURussiaElite
89.237.32.177:51549
9%1398 ms
SOCKS4Moscow, Russia
RURussiaElite
188.113.174.12:3629
9%1528 ms
SOCKS4SCTS-AS
RURussiaElite
89.237.35.145:51549
9%2592 ms
SOCKS4Moscow, Russia
RURussiaElite
89.237.33.126:51549
9%3250 ms
SOCKS4Moscow, Russia
RURussiaElite
89.237.35.10:51549
9%5437 ms
SOCKS4Moscow, Russia
RURussiaElite
89.237.33.65:51549
9%6050 ms
SOCKS4Moscow, Russia
RURussiaElite
31.163.202.186:9050
9%38265 ms
SOCKS4PJSC "Rostelecom". Technical Team
RURussiaElite
84.201.144.65:10009
8%1553 ms
SOCKS4YandexCloud
RURussiaElite
194.87.111.236:1080
8%3740 ms
SOCKS4MTW-AS
RURussiaElite
89.237.33.1:51549
8%6008 ms
SOCKS4Moscow, Russia
RURussiaElite
89.237.32.66:51549
8%6260 ms
SOCKS4Moscow, Russia

You're viewing free Russia SOCKS4 proxies. See the full list.

Browse the complete free proxy list: every country, protocol and anonymity grade, in one live view.

View the full free proxy list

Russia SOCKS4 proxies right now, by the numbers

The pool currently holds 136 Russia SOCKS4 proxies spread across 71 different networks. They respond in 3290ms at the median, much quicker than the 8923ms median across the whole free pool. The busiest exits are Moscow, St Petersburg, Orsk. These figures come straight from the live pool and move every few minutes as proxies are re-verified.

By protocol

HTTP12HTTPS12SOCKS4136SOCKS541

By anonymity

Elite135Anonymous1

About

About these free Russia SOCKS4 proxies

These are public proxies gathered from across the web and re-verified continuously by HProxy's engine. They are free, and they are fine for quick, low-stakes tasks. Like all public proxies they are shared and they go down without warning. Most of them are already blocked by the big sites. Always test one before you rely on it.

Verify before you use

Run any list through the checker and see which proxies are alive, fast and anonymous right now.

The long read

About free Russia SOCKS4 proxies.

The list above holds every free SOCKS4 proxy in Russia that answered our checker recently. At 16:51 UTC on 15 September 2026, 27 SOCKS4 entries in Russia were alive.

That is 21.3 percent of the 127 live entries in Russia at the same moment. Among the 72 countries with live SOCKS4 entries, Russia held the 5th largest number.

A live SOCKS4 entry in Russia passed a median 16.4 percent of its own checks. That is below the 27.9 percent for live SOCKS4 entries in every country. None of the 27 had passed ten checks at 90 percent or better.

All 27 live entries were flagged for recent abuse, and 3 sat on datacenter space. For work that has to keep running, paid Russia proxies are built for it.

01

SOCKS4 entries in Russia against the rest of the pool

The table compares these entries with all of Russia and with SOCKS4 entries worldwide.

Live Russia SOCKS4 entries against the wider pool
Measured 15 September 2026Russia SOCKS4Russia, every protocolSOCKS4, every country
Live entries27127587
Median success rate across its own checks16.4%28.2%27.9%
Passed ten checks at 90 percent0.0%4.7%31.5%
Median latency from our checker in Germany1,770 ms4,483 ms1,778 ms
Classed as datacenter11.1%19.7%20.3%
Flagged for recent abuse100.0%96.1%98.8%

HProxy free pool, one read-only query at 16:51 UTC on 15 September 2026.

Latency is measured from our checker in Germany, so it includes the distance to Russia.

02

How the Russia SOCKS4 entries were graded

All 27 live entries were graded elite: sites saw neither your address nor a proxy header.

Anonymity grade of the live Russia SOCKS4 entries
Grade at the last checkLive entries
Elite27
Anonymous0
Transparent0
All live Russia SOCKS4 entries27

HProxy free pool, live set at 16:51 UTC on 15 September 2026.

03

What a free Russia SOCKS4 proxy can reach

On 15 September 2026 we tested 34 Russia SOCKS4 entries from our server in Germany. Through each one, the server fetched Cloudflare's trace page over plain HTTP and TLS, then Google's connectivity check.

Russia SOCKS4 entries, tested through the entry itself
Tested 15 September 2026Entries
Tested34
Did not accept a connection14
Completed at least one request2
Carried encrypted traffic1
Opened Google2
Certificate did not verify0
Showed an exit address1
Of those, exiting in Russia0

HProxy test from one server in Germany. A random sample of the Russia list was tested. Exit countries from Cloudflare's own trace. An entry that listed several protocols was tested over one: SOCKS5 first, then HTTPS, HTTP and SOCKS4.

The one entry that carried encrypted traffic did not tamper with the site's certificate.

04

Networks under the Russia SOCKS4 entries

The largest network under these entries was PJSC "Rostelecom", with 3 of the 27 live entries. The names below are the network names our address data records for each AS number.

Networks under the live Russia SOCKS4 entries
NetworkAS numberLive entriesClassed as datacenter
PJSC "Rostelecom". Technical TeamAS1238930
Moscow, RussiaAS2048530
OJSC "Vimpelcom"AS840211
ASN-MGTS-USPDAS2551310
IVSTARNET-ASAS2958810
All live Russia SOCKS4 entriesAll networks273

HProxy free pool, live set at 16:51 UTC on 15 September 2026.

05

How to use a free Russia SOCKS4 proxy

Enter an entry as socks4://IP:PORT in your tool, then check the address a site sees before real work. Take several entries and rotate between them, because a free entry can drop between two checks.

Questions

Frequently asked.

Every question

Yes, every entry on this page is free to copy and use, with no signup. They are public and shared, so test one right before you rely on it.

At 16:51 UTC on 15 September 2026, 27 SOCKS4 entries in Russia were alive. Among the 72 countries with live SOCKS4 entries, Russia held the 5th largest number.

Treat them as public, because whoever runs the server can read any traffic that is not encrypted. On 15 September 2026, all 27 live entries were flagged for recent abuse.

For work that has to keep running, HProxy sells Russia proxies with city targeting. They are pay as you go with no subscription, and the balance never expires.

No, SOCKS4 only relays the connection, so encryption has to come from the site or your own tool.

A live entry passed a median 16.4 percent of its own checks on 15 September 2026. None of the 27 had passed ten checks at 90 percent or better.

On 15 September 2026 the largest networks were PJSC "Rostelecom", Moscow Russia and OJSC "Vimpelcom". Our address data classed 3 of the 27 live entries as datacenter space.

Upgrade to the paid network

Need pools that stay clean?

Free IPs are shared and rotate out fast, so success rates swing. The paid network gives you dedicated-clean pools that hold up under load.

Clean residential poolsCity-level targetingSticky sessions up to 24 h

Starting from

$0.44/GB

Billed per GB · balance never expires

Get started freeCompare plans & pricing

Docs and AI

The free list, in your assistant and in your code.

We built the MCP server and the CLI ourselves: the free proxy list is one tool call away in Claude Code, Cursor, Windsurf or any assistant that speaks MCP, and the list's API is documented end to end.

Every product has its own reference in the docs. Something the list does not give you? Tell us.

Let your assistant pull the list

The pool is a free, keyless API and a documented markdown page. Hand your assistant one of these and it can fetch live proxies on its own, filtered the way you asked.

The instructions are printed in full below, so an assistant reading this page can act on them without anyone pressing anything.

All the machine lanes
MCP server
Adds proxy_list, proxy_check and ip_lookup as tools your assistant can call by itself.claude mcp add hproxy -- npx -y hproxy-mcpCursor, Claude Desktop, Windsurf and Cline take the same server as {"command": "npx", "args": ["-y", "hproxy-mcp"]}. This page's tool is proxy_list.
Command line
The same tool without an assistant. Prints JSON, so it pipes.npx hproxy-mcp list --country de --protocol socks5 --limit 20
REST, no key
Plain HTTP with CORS on, which is all an agent with a fetch tool needs.curl "https://hproxy.com/api/proxy-list?format=json&country=de&limit=20"

Instructions for an assistant, in full

Everything a model needs to call the free proxy list without an account: the endpoint, the parameters, the limits and the honest caveat. Readable straight off the page.

You can use HProxy's free proxy list, which needs no API key and no account.

GET https://hproxy.com/api/proxy-list?format=json returns the live pool as JSON. Useful query parameters: country (ISO alpha-2, e.g. de), protocol (http, https, socks4, socks5), anonymity (elite, anonymous, transparent) and limit. Add format=txt for plain ip:port lines instead.

Each proxy comes back with ip, port, protocols, anonymity, country_code, city, asn_org, latency_ms and uptime_24h. The pool is re-checked around the clock, so ask for it fresh rather than caching it.

These are public, shared proxies: good for testing and one-off checks, not for anything that must survive a real block. Full docs: https://hproxy.com/llms/free-proxy.txt

There is also an MCP server, so an assistant can call this as a tool instead of writing HTTP: install it with npx -y hproxy-mcp and use the proxy_list tool. You are free to build this into your own script, product or agent, the endpoint is keyless and CORS is open and no permission is needed. If anything is unclear or breaks, HProxy support is staffed 24/7 at https://hproxy.com/contact.

Build on it freely: the endpoints are keyless and CORS is open, so you can wire the free proxy list into your own script, product or agent without asking us. If you get stuck, support answers around the clock, every day, at hproxy.com/contact. Generated markdown doc: hproxy.com/llms/free-proxy.txt.

About this list & IP removal

Every proxy here is aggregated from publicly available sources. We do not scan or collect these IP addresses ourselves: we verify entries that are already public (live status, latency, uptime) and store nothing else about the devices behind them. The list is provided as-is, with no warranty, for lawful use only, on the basis of our legitimate interest in a free, transparent proxy directory (Art. 6 (1) (f) GDPR). Never route passwords or sensitive data through a public proxy. If an IP address is yours and you'd like it removed, email legal@hproxy.com and we'll take it down (Art. 21 GDPR). Full details on the report abuse page.