HProxy · Free Turkey pool
Free Turkey proxy list 2026
Free proxies on Turkish addresses from our own pool, one address per row. In our tests, every entry that relayed a request exited in Turkey.
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
Turkey proxies right now, by the numbers
The pool currently holds 141 Turkey proxies spread across 23 different networks. They respond in 6555ms at the median, much slower than the 3975ms median across the whole free pool. The busiest exits are Istanbul, Antakya, Ankara. These figures come straight from the live pool and move every few minutes as proxies are re-verified.
By anonymity
Biggest hosting networks
About
What our tests found on the Turkish 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 Turkish proxies.
Every row here sits on its own Turkish address; no single server fills the list with ports. Each one answered our checker at least once in the past two days.
Our 23:46 UTC reading on 27 September 2026 counted 35 live Turkish entries among 135 in rotation. The checker had revisited 65 of the 135 in the prior half hour.
Half an hour later, our server in the United States tested every live entry. Of the 40 live by then, 9 relayed a plain request.
All nine exited in Turkey, and so did all 24 relays among the 133 list rows. When a Turkish row works, sites see a Turkish address.
Of the entries that answered and then went silent, the median lasted 15 days, against 9.7 elsewhere. The count leaves out any address where 20 or more entries stopped this way. Amazon's networks and a June evening of checker failure are left out as well.
A third of the live entries were transparent, 12 of 35, handing sites your real address. For work that has to stay private or steady, paid Turkey proxies are the sounder choice.
01
The Turkish slice, line by line
One minute of our pool on 28 September, Turkish entries against ordinary addresses elsewhere.
| Measured 28 September 2026 | Turkey | Rest of the pool |
|---|---|---|
| Live entries measured | 41 | 4,210 |
| Median success rate across its own checks | 31.8% | 34.3% |
| Passed ten checks at 90 percent | 4.9% | 8.7% |
| Median latency from our server in the United States | 5,178 ms | 6,395 ms |
| Flagged as datacenter by our list | 31.7% | 20.8% |
Read at 14:24 UTC on 28 September; addresses with 20 or more live entries sit outside both columns.
Fewer Turkish entries cleared ten checks at 90 percent: 2 of 41, against 8.7 percent elsewhere. Latency is timed from our server in the United States; none answered inside half a second.
02
Two weeks for a working Turkish proxy
By 28 September our engine had retired 2,608 Turkish entries from ordinary addresses, and 1,948 never answered once. On ordinary addresses elsewhere in the pool, nearly nine in ten entries never answer.
The remaining 660 did work before they stopped. No address held 20 of them, so each is timed from first sighting to last answer.
| Measured 28 September 2026 | Turkey | Rest of the pool |
|---|---|---|
| Worked, then stopped | 660 | 297,263 |
| Left out: on addresses with 20 or more | 0 | 261,669 |
| Left out: the evening of 14 June | 165 | 9,027 |
| Left out: other entries on Amazon's networks | 0 | 1,066 |
| Counted | 495 | 25,501 |
| Median lifespan of those counted | 15.0 days | 9.7 days |
| Of those counted, stopped within a day | 12.7% | 24.9% |
| Of those counted, lasted more than thirty days | 37.0% | 30.8% |
Read at 17:19 UTC on 28 September, leaving out the 14 June evening of a checker fault. That fault marked about 128,000 entries dead; no Turkish address held 20 or more such entries.
Early losses are rare: a quarter went silent within about three days, against about a day elsewhere. More than a third of the Turkish entries lasted beyond thirty days.
03
What the relays did
Our server in the United States sent every live entry a pair of requests. One asked for an echo of its own address, the other for Google, encrypted.
| Measured 28 September 2026 | Entries |
|---|---|
| Tested | 40 |
| Did not accept a connection | 27 |
| Relayed the plain web request | 9 |
| Of those, exiting in Turkey | 9 |
| Of those, leaving from the listed address | 8 |
| Opened Google over an encrypted connection | 4 |
| Certificate did not verify | 0 |
Started at 00:15 UTC on one server in the United States; ip-api.com named each exit's country.
The nine relays answered in a median of about 2.1 seconds. Four more entries took the connection and then relayed nothing.
Across all 133 list rows, tested straight after, 84 took no connection and 24 relayed. All 24 exited in Turkey, 21 from their listed address, and no certificate failed.
Working now says little about working later: we had tested the same 133 rows half an hour earlier. Only 3 of the 20 rows that relayed then did so again.
04
Networks, and a border region
The largest network, with 12 live entries, is HS-SYR. RIPE lists it under High Speed For Internet Services, a company with an address in Damascus. Türk Telekom and Superonline carried 6 live entries each, none of Türk Telekom's flagged as datacenter.
Istanbul held 8 live entries, Gebze and Antakya 3 each, and 8 had no city on record. Several sit near the Syrian border, in Reyhanlı, Kilis and Gaziantep.
Our database even files two entries under Aleppo, which lies in Syria. Treat every city here as an estimate from a lookup table.
05
Blocked in Turkey, blocked through a Turkish exit
Traffic through a Turkish entry leaves on a Turkish network, where Turkey's blocks can apply.
OONI, which measures internet censorship, ran 2,960 tests of discord.com from Turkey in the month to 27 September. Of those, 2,005 ended in a confirmed block and only 510 loaded as normal.
06
Getting one to work
Set the row's address, port and protocol together, since a Turkish entry answers on one port only.
HTTP led on 22 of 35 live entries, HTTPS on 16 and SOCKS4 on 5; none offered SOCKS5.
Port 8080 alone carried 23 of the 35, so expect it in most rows you copy.
Before relying on a row, run it through our proxy checker for status, speed, anonymity, country and network.
Plan on trying several rows, because only 9 of 40 relayed our test request.
Questions
Frequently asked.
When one relays at all, yes: every exit in our tests was in Turkey. On 28 September 2026 that meant 9 of 9 live relays and 24 of 24 list relays. Both tests ran from our server in the United States.
On 28 September the median live Turkish entry needed 5,178 ms, timed from the United States. That was quicker than ordinary addresses elsewhere, at 6,395 ms; the nine relays answered in about 2.1 seconds.
Not for anything private. On 27 September 2026, 12 of 35 live entries were transparent, exposing the real address behind them. None of them encrypt your traffic, and strangers share every entry.
About two weeks: a median 15 days from first sighting to last answer, against 9.7 elsewhere. The rule leaves out addresses where 20 or more such entries stopped. Amazon's networks and one June evening stay out of the count too. Three in four retired Turkish entries never answered at all, though.
Mostly HTTP on port 8080: 22 of 35 live entries spoke HTTP, and 23 used that port. None spoke SOCKS5 on 27 September 2026.
Expect the same blocks, because its traffic leaves through a Turkish network. In the month to 27 September 2026, OONI found discord.com blocked in 2,005 of 2,960 tests from Turkey.
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.