HProxy · Free Russia pool
Free Russia proxy list 2026
Public proxies on Russian addresses, with the uptime and speed our checker measured for each. Rows with high uptime worked far more often in both our tests.
Every slice of the pool
The same live list, one thing at a time.
A page per country, protocol, anonymity grade, operator, port, network and block, each with its own count, download and API call.
Free proxies by country
24 pages
Russia proxies right now, by the numbers
The pool currently holds 500 Russia proxies spread across 218 different networks. They respond in 4469ms at the median, slower than the 3451ms median across the whole free pool. The busiest exits are Moscow, St Petersburg, Perm. These figures come straight from the live pool and move every few minutes as proxies are re-verified.
By anonymity
About
What we measured on the Russian list
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 Proxy Checker, in the free app or online, and see which proxies are alive, fast and anonymous right now.
The long read
About free Russian proxies.
Each row is a public proxy our checker places in Russia and heard from within two days. Of the rows that relayed our test request, most gave a Russian address and some a foreign one.
Our pool held 594 Russian entries in rotation at 21:17 UTC on 27 September 2026. 129 were passing checks at that minute, and 288 had been checked within half an hour.
Four hours later, at 01:20 UTC, 132 entries were live. Our server in the United States sent one plain web request through each. 40 relayed it: ip-api.com placed 35 of those exits in Russia and 5 in three other countries.
Most of the Russian list sits outside datacenter space, by our list's own flag. Only 26 of the 129 live entries carried that flag, level with ordinary addresses elsewhere.
Of the Russian entries that worked and then stopped, the median one lasted 5.4 days, against 10.0 elsewhere. Both medians count only the addresses with fewer than 20 such entries. Entries on Amazon's networks are out of both, and so are those of one faulty June evening.
19 of the 129 were graded transparent, so the site still learns your own address. When a job needs a Russian address every day, use paid Russia proxies instead.
01
Five measures, Russia against the rest of the pool
Each line was read at 14:43 UTC on 28 September, for Russian entries and ordinary addresses elsewhere.
| Measured 28 September 2026 | Russia | Rest of the pool |
|---|---|---|
| Live entries measured | 124 | 4,007 |
| Median success rate across its own checks | 36.1% | 33.8% |
| Passed ten checks at 90 percent | 3.2% | 9.0% |
| Median latency from our server in the United States | 5,436 ms | 6,446 ms |
| Flagged as datacenter by our list | 21.0% | 20.8% |
Busy addresses, with 20 or more live entries each, are left out of both columns; Russia had none.
Russian entries answered a little faster and passed slightly more checks, yet fewer cleared ten at 90 percent. Those times were measured from our server in the United States, so yours will differ. Just 1 of the 124 answered within half a second, and 87 took three seconds or more.
02
How long a Russian free proxy keeps working
Our engine had given up on 12,182 Russian entries on ordinary addresses, and 10,392 had never answered. That is 85 percent, a little better than the 88.8 elsewhere.
Counting every address, 1,878 worked for a while and then stopped, 88 of them on just two addresses. We drop any address with 20 or more such entries; the table shows what that leaves.
We time each entry from the day we first saw it to the day it stopped answering.
| Measured 28 September 2026 | Russia | Rest of the pool |
|---|---|---|
| Worked, then stopped | 1,883 | 296,040 |
| Left out: on addresses with 20 or more | 88 | 261,581 |
| Left out: the evening of 14 June | 208 | 8,984 |
| Left out: other entries on Amazon's networks | 0 | 1,066 |
| Counted | 1,587 | 24,409 |
| Median lifespan of those counted | 5.4 days | 10.0 days |
| Of those counted, stopped within a day | 26.4% | 24.6% |
| Of those counted, lasted more than thirty days | 24.3% | 31.4% |
Read at 17:19 UTC on 28 September; only addresses with fewer than 20 such entries count. Also out: the evening of 14 June, when our checker's fault marked about 128,000 entries dead.
The difference is at the long end: in both groups a quarter were gone within about a day. Past thirty days, though, 24.3 percent of Russian entries lasted, against 31.4 elsewhere.
03
Where a Russian entry sends your request
Our test asked each live entry for a plain page that reports the address it sees. A second request went to Google, with the connection encrypted end to end.
| Measured 28 September 2026 | Entries |
|---|---|
| Tested | 132 |
| Did not accept a connection | 47 |
| Relayed the plain web request | 40 |
| Relayed it and exited in Russia | 35 |
| Exited in Russia from the listed address | 34 |
| Exited in another country | 5 |
| Opened Google over an encrypted connection | 24 |
| Certificate did not verify | 0 |
Tested from one server in the United States at 01:20 UTC, with exit countries by ip-api.com.
Half of the 40 relays answered within about 2.5 seconds. By city, 14 Russian exits sat in Moscow and 3 in St Petersburg. The other 18 were spread over 17 towns, from Krasnodar to Sakhalin.
The 5 foreign exits were in Kazakhstan, the United States and Canada. One was the listed address itself: our list places it in Moscow, ip-api.com in Almaty.
04
Picking a row that works
The list keeps a row for 48 hours after its last success: 553 rows at 01:20 UTC. A minute later, our server in the United States tested all 553, and none showed a bad certificate.
340 did not accept a connection, and 88 relayed a request, 82 of them exiting in Russia.
Uptime pointed to the rows that worked: 34 of the 73 showing 50 percent or more relayed. Of the 480 rows that showed less than 50 percent, only 54 relayed our request.
Our first test, four hours earlier, sent SOCKS4 rows a request form many refuse. Its other rows showed the same pattern: 32 of 70 against 43 of 395.
| Uptime on the list | Entries | Relayed a request |
|---|---|---|
| Under 10 percent | 89 | 5 |
| 10 to 24 percent | 252 | 30 |
| 25 to 49 percent | 139 | 19 |
| 50 to 74 percent | 49 | 21 |
| 75 percent or more | 24 | 13 |
Our test of all 553 entries from one server in the United States, 01:21 UTC, 28 September 2026. Uptime is the figure the list showed at 01:20 UTC.
Sort by uptime before you copy: in both tests, high-uptime rows relayed about four times as often. Even so, more than half of them failed.
05
The networks behind the Russian list
These counts come from the reading of 21:17 UTC on 27 September.
Rostelecom carried 10 live entries, more than any other network, then Beget 6 and TimeWeb 5. Our list flagged all five TimeWeb entries as datacenter space. VimpelCom carried 4 and MTS 3, and our list flagged none of those seven.
Each operator name comes from the network's record at RIPE, the regional internet registry that covers Russia.
By city, Moscow held 37 live entries and St Petersburg 17, while 33 had no city on record. Every city is a database estimate, not a fact about the machine.
06
What a Russian address means for blocked sites
A Russian exit reaches the web through a Russian network, so Russian blocking can apply to it.
OONI is a project whose volunteers measure internet censorship around the world. In the month to 27 September, they tested www.instagram.com from Russia 53,290 times. 3,534 tests were confirmed blocked, and fewer than a quarter loaded normally.
07
Setting up a free Russian proxy
Your tool needs three values from the row: its address, its port and its protocol.
Of the 129 live entries, 80 spoke HTTP, 36 HTTPS, 22 SOCKS4 and 20 SOCKS5. Some spoke several.
Port 8080 served 25 of them, 1080 served 21 and 3128 served 19.
Before real work, paste the entry into our proxy checker to see how it behaves. It reports status, speed, anonymity, country and network, all measured through the proxy.
Keep two or three spare rows at hand, because many entries stop without warning. More than a quarter of the Russian entries counted above stopped within their first day.
Questions
Frequently asked.
Most of the working ones do, but not all of them. On 28 September 2026, 40 of 132 live entries relayed our request from the United States. By ip-api.com, 35 of those exits were in Russia and 5 in other countries.
Slightly faster than the typical free entry, though real work would find them slow. From the United States on 28 September, our checker measured a median 5,436 ms for live Russian entries. Ordinary addresses elsewhere came in at 6,446 ms, and just 1 Russian entry beat half a second.
Only for public pages, never for a login or a payment. On 27 September 2026, 19 of 129 live entries passed the real address on to the site. Free entries take no login, so strangers can share the same entry with you. The person running an entry can read every page you load without HTTPS.
A median of 5.4 days from our first sighting to its last answer, against 10.0 for the rest. Those medians leave out any address with 20 or more such entries, Amazon's networks and one June evening. Most Russian entries never work at all: 85 percent of those we set aside never answered once.
Set whatever the row lists, since each row is one address, one port and its protocols. On 27 September 2026, port 8080 led with 25 live entries, ahead of 1080 and 3128. 80 of the 129 spoke HTTP, far ahead of any other protocol.
Free entries come and go between checks, and a row stays listed for two days. Our server in the United States found 340 of the 553 listed rows taking no connection. Rows showing 50 percent uptime or more relayed our request 34 times out of 73.
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.
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, ChatGPT, Cursor 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.
Claude, ChatGPT, Cursor, Gemini, Copilot, Windsurf, Perplexity, Ollama and any assistant that speaks MCP.
MCP server
Built by us and hosted at mcp.hproxy.com: the free proxy list, the checker and the IP lookup as tools in Claude, ChatGPT, Cursor, VS Code or any assistant that speaks MCP. Nothing to install, no key.
CLI
The list from a terminal: hproxy list --country DE --limit 20, from the command line of the free HProxy app.
API docs
The free list's API, documented end to end with real responses: the filters, the formats, the limits.
llms.txt
The whole documentation as markdown for any model that reads: /llms.txt for the index, /llms-full.txt for everything.
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. Nothing to install.
claude mcp add --transport http hproxy https://mcp.hproxy.com/mcpClaude, ChatGPT, Cursor, VS Code, Windsurf or any assistant that speaks MCP: add https://mcp.hproxy.com/mcp as a remote server. This page's tool is proxy_list. - Command line
- The same tool without an assistant, from the free HProxy app's command line. Add --json for JSON.
hproxy list --country DE --protocol socks5 --limit 20Comes with the free HProxy app: hproxy.com/proxy-checker - 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: add https://mcp.hproxy.com/mcp as a remote MCP server (nothing to install, no key) and use the proxy_list tool. In Claude Code the line is `claude mcp add --transport http hproxy https://mcp.hproxy.com/mcp`. 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.