HProxy · Free Mexico pool
Free Mexico proxy list 2026
Free proxies on Mexican addresses from our own pool, spread over many states and small networks. In our tests, every relay exited inside Mexico.
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.
Mexico proxies right now, by the numbers
The pool currently holds 466 Mexico proxies spread across 68 different networks. They respond in 4817ms at the median, slower than the 3669ms median across the whole free pool. The busiest exits are Queretaro City, Zimapan, Morelia. These figures come straight from the live pool and move every few minutes as proxies are re-verified.
By anonymity
About
What our tests found on the Mexican 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 Mexican proxies.
Few of Mexico's free proxies sit in its capital. At 03:27 UTC on 28 September 2026, Mexico City held 2 of 110 live rows; Hidalgo held 19.
A minute earlier our pool counted 111 live Mexican entries among 462 in rotation. In the half hour before that reading, 188 of the 462 had received a check.
Only 7 of the 111 carried our datacenter flag, a far smaller share than elsewhere in the pool.
Our server in the United States then sent a request through each of the 110 live rows. Thirty passed it on, and every one of those exits sat in Mexico.
Nearly a third of the live entries were transparent, 35 of 111, and told each site your address. For steady or private work, paid Mexico proxies are the safer pick.
01
Mexican entries beside the rest of the pool
Both columns below come from one read at 13:09 UTC, and neither counts busy addresses.
| Measured 28 September 2026 | Mexico | Rest of the pool |
|---|---|---|
| Live entries measured | 106 | 3,920 |
| Median success rate across its own checks | 33.4% | 34.3% |
| Passed ten checks at 90 percent | 0% | 9.2% |
| Median latency from our server in the United States | 5,639 ms | 6,329 ms |
| Flagged as datacenter by our list | 8.5% | 22.2% |
Read at 13:09 UTC without addresses holding 20 or more live entries; no Mexican address held that many.
Mexican entries passed slightly fewer checks, and none had cleared ten at a 90 percent rate. Just one answered our checker within half a second.
02
Small networks across the country
No single network dominates: Total Play carried 9 live entries and IENTC 8, and none carried more.
Transtelco held 5, while GTT, Alestra, Uninet and Telecomunicaciones Otomíes held 4 apiece.
Zimapán led the towns with 8 live entries, Morelia had 6 and Tulancingo 4; ten had none.
03
What our relay test found
Through each live row, our server asked ip-api.com for the exit address and tried Google, encrypted.
| Measured 28 September 2026 | Entries |
|---|---|
| Tested | 110 |
| Did not accept a connection | 72 |
| Relayed the plain web request | 30 |
| Of those, exiting in Mexico | 30 |
| Of those, leaving from the listed address | 17 |
| Opened Google over an encrypted connection | 17 |
| Certificate did not verify | 0 |
One server in the United States, starting at 03:27 UTC; ip-api.com placed every exit.
The thirty relays needed a median of about 5.9 seconds; 8 more rows connected and passed nothing on.
Next we tried all 425 rows of the 48-hour list. Away from three Amazon addresses, 365 rows gave 68 relays, all inside Mexico.
Thirty-eight minutes on, a second pass saw 41 of 131 live rows relay, and 66 list rows. Only 23 of the first pass's 68 list relays repeated, and the Amazon rows again relayed nothing.
04
Three Amazon addresses to skip
Sixty of the 425 list rows sat on just three addresses: 78.12.136.220, 78.12.246.160 and 78.14.19.3.
ARIN files all three under AMAZON-QRO, held by Amazon Data Services Mexico; our database places them in Querétaro.
None of the 60 relayed our request, and 40 showed a certificate that failed verification. A browser would warn that such a connection is not private.
A second pass found 58 rows there, again without one relay.
By 13:09 UTC our engine had retired 924 entries that worked on 15 Amazon addresses there.
05
Long lives once they work
Of 2,291 Mexican entries retired from ordinary addresses, 1,753 never answered a single check.
That is three in four, against 88.7 percent on the pool's other ordinary addresses.
Of the 1,465 that worked, 925 sat on those busy Amazon addresses; our lifespan rule skips such addresses.
| Measured 28 September 2026 | Mexico | Rest of the pool |
|---|---|---|
| Worked, then stopped | 1,465 | 296,458 |
| Left out: on addresses with 20 or more | 925 | 260,744 |
| Left out: the evening of 14 June | 159 | 9,033 |
| Left out: other entries on Amazon's networks | 0 | 1,066 |
| Counted | 381 | 25,615 |
| Median lifespan of those counted | 19.0 days | 9.7 days |
| Of those counted, stopped within a day | 12.1% | 24.9% |
| Of those counted, lasted more than thirty days | 39.6% | 30.8% |
Read at 17:18 UTC. It skips the evening of 14 June, when a checker fault marked some 128,000 entries dead.
Counted entries lasted a median 19 days, about twice the pool's 9.7; two in five passed thirty days.
06
Thin filtering on Mexican networks
OONI's volunteers, who measure censorship, ran 547,176 web tests from Mexico in the month to 28 September.
Of those, 96.6 percent loaded normally, and confirmed blocks touched only 144 of 2,352 sites. No site with 100 tests or more was confirmed blocked in over 5 percent of them.
When a page will not load through a Mexican row, the row is the likely cause.
07
Setting up a Mexican row
Expect port 999: it served 81 of the 111 live entries, far ahead of 3128 with 6.
HTTP and HTTPS each ran on 68 live entries, SOCKS4 on 6 and SOCKS5 on a single one.
A quick run through our proxy checker shows whether a row still answers, and how fast.
A quarter to a third of live rows relayed for us: 30 of 110, then 41 of 131.
The Uptime column helps: rows showing 50 percent or more relayed over twice as often, in both passes. Most of those rows still failed, and the comparison sets the Amazon rows aside.
Give a failed row a second try: most rows that relayed for us managed it only once.
Questions
Frequently asked.
It did whenever one worked for us: 205 relays over four tests, and not one left Mexico. All four tests ran on 28 September 2026, sent from one server in the United States.
At 13:09 UTC, the median live entry took 5,639 ms to answer our checker in the United States. Entries on the pool's ordinary addresses needed 6,329 ms, and our thirty relays about 5.9 seconds.
Not for logins, payments or anything private: 35 of 111 live entries were transparent on 28 September 2026. Forty Amazon rows on the list also showed certificates that failed verification.
Working entries lasted a median 19 days, against 9.7 across the rest of the pool. Addresses with 20 or more such entries stay out, among them 15 on Amazon with 925. Other Amazon entries and one June evening when our checker failed are left out too.
Mostly port 999, which 81 of the 111 live entries used on 28 September 2026. HTTP and HTTPS each ran on 68 of them.
Seldom: Mexico City held 2 of 110 live rows at 03:27 UTC, both datacenter, and Guadalajara none. Hidalgo held 19, and any town on the list is a database estimate.
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.