HProxy · Free Colombia pool
Free Colombia proxy list 2026
Free proxies on Colombian addresses, re-checked around the clock. Few answer, but every row that relayed our request came out inside Colombia.
ColombiaTransparentYou're viewing free Colombian proxies. See the full list.
Browse the complete free proxy list: every country, protocol and anonymity grade, in one live view.
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
Colombia proxies right now, by the numbers
The pool currently holds 500 Colombia proxies spread across 60 different networks. They respond in 5644ms at the median, much slower than the 2427ms median across the whole free pool. The busiest exits are Medellin, Pereira, Bogota. These figures come straight from the live pool and move every few minutes as proxies are re-verified.
By anonymity
About
Colombia's free list, relay by relay
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 Colombian proxies.
Colombia's free list is long, and what works on it really is Colombian. Every one of the 76 rows that relayed our request came out inside Colombia.
The catch is how few work. In our test at 10:16 UTC on 28 September 2026, 322 of the 444 rows took no connection.
Even the 144 rows marked live fared poorly from our server in the United States. Ninety-two let our connection time out, and only 35 relayed a request.
Most live rows sit on internet provider networks, not in data centers, and most use port 999. Colombian entries that do work tend to last about a month.
When a Colombian job cannot wait for a row that works, paid Colombia proxies are the steadier choice.
01
Colombia against the rest of the free pool
Both columns come from read-only queries of our pool on 28 September 2026.
| Measured 28 September 2026 | Colombia | Rest of the pool |
|---|---|---|
| Live entries measured | 144 | 4,132 |
| Median success rate across its own checks | 26.8% | 33.8% |
| Passed ten checks at 90 percent | 2.8% | 8.8% |
| Median latency from our server in the United States | 7,610 ms | 6,010 ms |
| On datacenter address space | 9.0% | 21.4% |
| Retired entries that never answered once | 84.8% | 88.7% |
| Median lifespan of entries that died | 746 hours | 228 hours |
| Died within a day | 6.4% | 25.0% |
| Lasted more than 30 days | 50.7% | 30.6% |
Colombia's live figures date from 10:16 UTC, the rest column's other rows from 10:43, every lifespan from 17:18. Each row leaves out addresses holding 20 or more of the entries it counts. Lifespans run from first sighting to last answer, skipping Amazon's networks and the June evening our checker failed.
Most Colombian entries never worked at all, yet those that did outlasted the pool's by weeks.
Half of the working ones ran for more than 30 days, against under a third across the rest.
Entries elsewhere in the pool passed more of their checks, though, and answered our checker faster.
02
Every relay stayed in Colombia
Our test tried to connect to all 444 rows. Through each row that answered, it requested an address echo, a Cloudflare page and a Google page.
All 76 relays came out in Colombia, 21 of them in Bogotá by ip-api.com's reckoning. Cloudflare placed all 40 of its answers in Colombia, though it served 14 from Miami.
Only 31 of the 76 relays left from the very address our list shows. The other 45 used another Colombian address, and 24 of those stayed with the same provider.
The Tor Project's own check reached 13 of the relays, and none of them was on Tor.
03
Networks and ports behind the Colombian rows
Our datacenter flag marked just 13 of the 144 live entries, under half the share elsewhere.
Ufinet held 22 live entries, Super Redes 19 and TV Azteca 13. Media Commerce, EPM and Internexa followed with 12 each.
Port 999 carried 103 of the 144 live entries and 57 of the 76 relays.
04
How to use a free Colombian proxy
Expect most rows to fail, and try several: in our test, one row in six relayed a request.
At 50 percent Uptime or more, about one row in four relayed: 8 of 27, then 7. Below that, 68 of 417 relayed in the first test and 61 in the second.
The 23 SOCKS4 rows did best in both tests, relaying 5 and then 10.
Copy the address, the port and the protocol together, and check the exit before you rely on it.
Every certificate that reached us through a Colombian row passed its check in our test. Keep to HTTPS sites all the same, and never sign in to an account through a free row.
Questions
Frequently asked.
Yes, and there is nothing to sign up for: copy a row and use it. Other people share each row, so test one right before you need it.
Most never worked at all: 84.8 percent of the Colombian entries we retired had not answered once. In our test, 322 of 444 rows took no connection.
Measured from the United States, a typical live Colombian entry needed 7,610 ms to answer. That is slower than the 6,010 ms elsewhere in our pool, busy addresses left out. Relays through Colombian rows took a median 7.6 seconds in our own test.
Our location data put 38 live entries in Medellín and 12 in Bogotá. A relay often exits elsewhere, though: only 29 of 76 came out in the town the list showed.
In our test on 28 September 2026, all 76 rows that relayed our echo came out in Colombia. We sent every request from our server in the United States.
Not for logins, payments or anything else private. Whoever runs a row sees the sites you visit and can alter any page sent without HTTPS. Our checker also found 48 of the 144 live entries transparent, which hands each site your real address.
Longer than most: working Colombian entries lasted a median 746 hours, about a month, against 228 elsewhere. Neither side counts busy addresses or Amazon's networks, and one June evening when our checker failed is skipped.
HProxy sells Colombia residential proxies with in-country targeting, billed as you go and never by subscription. Purchased traffic has no scheduled expiry date, so gigabytes bought for one job can wait for the next.
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 a terminal. Add --json for JSON.
hproxy list --country DE --protocol socks5 --limit 20Install it in one line: curl -fsSL https://hproxy.com/install.sh | sh (macOS, Linux) or irm https://hproxy.com/install.ps1 | iex (Windows). - 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. It is rate limited per IP (120 requests in a burst, then 2 a second) and answers 429 with Retry-After past that.
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`. From a terminal the same tool is `hproxy list --country DE --protocol socks5 --limit 20`. Install the hproxy command in one line: curl -fsSL https://hproxy.com/install.sh | sh on macOS and Linux, or irm https://hproxy.com/install.ps1 | iex in PowerShell on Windows. 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.