HProxy · Free Canada pool
Free Canada proxy list 2026
The Canadian entries below all answered our checker within two days. More than four in five sat on Amazon addresses that relayed nothing in our test.
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
Canada proxies right now, by the numbers
The pool currently holds 499 Canada proxies spread across 24 different networks. They respond in 985ms at the median, quicker than the 1606ms median across the whole free pool. The busiest exits are Calgary, Montreal, Toronto. These figures come straight from the live pool and move every few minutes as proxies are re-verified.
By anonymity
Biggest hosting networks
About
The Canadian list up close
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 Canadian proxies.
This page lists the free Canadian proxies our checker heard from during the last two days. Pick a row, set its address, port and protocol, and check the exit before you rely on it. Our test saw a Canadian exit on 16 of the 19 entries that relayed a request.
At 02:30 UTC on 28 September 2026, Canada had 18 of the 18,144 live entries in our pool. Nearly nine in ten retired Canadian entries never gave a single answer: 16,387 of 18,651.
We tested 341 rows at 02:30 UTC; 280 sat on 12 Amazon addresses placed in Montreal and Calgary. Not one of those 280 carried a request anywhere. Our server could not verify the Cloudflare certificate that 119 of them presented.
Away from Amazon, 61 rows sat on 58 addresses in 22 networks. Nineteen relayed our echo, and 14 of those left from the listed address inside Canada. Two more came out of Cloudflare addresses in Toronto; three exited in Sydney or Frankfurt.
A live Canadian entry answered our server in the United States in 6.5 seconds at the median. Among entries that answered and later died, Canadian ones lasted about 14 days at the median, against 10. Before either median, addresses with 20 or more such entries were set aside, 23 of them Canadian. Entries on Amazon's networks were set aside too, as was one June evening when our checker failed. Jobs that need a Canadian address all day long belong on paid Canadian proxies.
01
Canada against the rest of the free pool
Busy addresses stay out of this comparison; the Canadian column is from 02:30 UTC.
| Measured 28 September 2026 | Canada | Rest of the pool |
|---|---|---|
| Live entries measured | 18 | 3,977 |
| Median success rate across its own checks | 54.3% | 34.5% |
| Passed ten checks at 90 percent | 11.1% | 9.0% |
| Median latency from our server in the United States | 6,521 ms | 6,389 ms |
| Answered in under one second | 27.8% | 6.8% |
| Median lifespan of entries that died | 339 hours | 235 hours |
| Died within a day | 24.6% | 24.7% |
| Lasted more than 30 days | 35.4% | 30.9% |
| Retired entries that never answered once | 94.9% | 88.5% |
Canada's live figures come from our 02:30 UTC read, the lifespans from 15:55 UTC. Everything else was read at 12:17 UTC, leaving out busy addresses. Lifespans follow entries that answered before dying, on addresses with fewer than 20 of them. They leave out Amazon's networks and the evening in June when our checker broke down.
Eighteen entries is a small sample, so one server can move any share in this table. Canadian entries die within a day about as often as elsewhere, and last past 30 days more often.
02
Twelve Amazon addresses behind 280 of 341 rows
Every one of the 341 Canadian rows the list API served at 02:30 UTC went through our test. Each row got three requests of up to 30 seconds: an echo service, Cloudflare and Google.
| Tested at 02:30 UTC, 28 September 2026 | On 12 Amazon addresses | On 58 other addresses |
|---|---|---|
| Entries on the list | 280 | 61 |
| Passed their latest check | 1 | 17 |
| Did not accept a connection | 0 | 13 |
| Completed at least one request | 0 | 28 |
| Relayed our echo with a visible exit | 0 | 19 |
| Exited in Canada from the listed address | 0 | 14 |
| Opened Google | 0 | 15 |
| Failed a certificate check | 119 | 0 |
All requests went out from one HProxy server in the United States. Exit countries come from ip-api.com, and Google here means its generate_204 connectivity check.
Each Amazon row answered at least one routine check in the last 48 hours, which keeps it listed. We returned to 90 of them at 02:32 UTC with a certificate probe. Seventy-five finished the encrypted handshake, and every certificate they showed named www.cloudflare.com.
Issuers named on them included DigiCert and Let's Encrypt, but also backup products like Veritas NetBackup and Commvault. All 32 that named a public authority were tested against that authority's own key, and every signature failed.
A plain page request drew 74 replies under 64 server names, each one reading: Could not connect. Who runs these 12 servers is not known to us. Their replies fit a honeypot better than a proxy. NIST's glossary compares a honeypot to honey for bears: a system designed to be attractive to intruders.
03
Where the Canadian relays came out
Fourteen of the 19 relays exited from the address on the list, all inside Canada. Three relays came out on Shaw, TELUS and Videotron, from Calgary, Delta and Montreal.
The three that left Canada all came out on OVH addresses, two in Sydney and one in Frankfurt. Our list had one of them in Montreal, one in Toronto, and one with no city.
Cloudflare answered 15 of its 19 traces from Toronto, Montréal and Vancouver. The other four came from data centers in Sydney, Los Angeles and Frankfurt. The Tor Project's own check reached 8 of the 19 relays, and none of those 8 was Tor.
04
How to use a free Canadian proxy
A row works only as a set: address, port and protocol go into your tool together. Skip the Amazon rows in Montreal and Calgary: none of the 280 carried traffic in our test.
Away from Amazon, rows showing 50 percent or more under Uptime relayed 8 of 15 in both tests. The other 46 relayed 11 each time, less than half that rate.
Through the entry, load an IP lookup page and read the country before anything real. Three of the 19 relays in our test came out in Australia or Germany.
A certificate warning means the entry does more than relay, so drop it and take another. A free SOCKS5 entry encrypts nothing on its own. Under RFC 1928, protection depends on the method agreed at the start; open entries pick no authentication.
A transparent entry hands the site your own address. Four of the 18 live Canadian entries carried that grade.
Keep several rows at hand, since any one of them can drop out between two checks. A quarter of the Canadian entries that died were gone in under 28 hours.
Questions
Frequently asked.
Yes, they cost nothing and need no account, but strangers share them; test one just before use.
Most rows relay nothing: 12 Amazon addresses held 280 of the 341 we tested, and none relayed.
About as quick as the rest: 6.5 seconds at the median, against 6.4 elsewhere, busy addresses aside. Both were timed from our server in the United States.
Sometimes: on 28 September 2026, Toronto held 5 of the 18 live Canadian entries and Montreal 3. Most rows the list places in Montreal or Calgary are the Amazon ones, and those carried nothing.
Mostly: our test on 28 September 2026 saw 16 Canadian exits among 19 relays. Australia and Germany took the other three.
Only for public pages: whoever runs an entry can read what you send unencrypted. Our test caught 119 Amazon rows answering Cloudflare with a certificate that failed verification. Send no passwords or card details through a free entry.
Of the Canadian entries that worked and then stopped, half had lasted about 14 days; elsewhere, about 10. About as many died within a day, 25 percent on both sides, and more passed 30 days. Neither figure counts addresses that lost 20 or more such entries, Amazon's networks or one June evening.
For steady Canadian work, HProxy sells residential, static ISP and datacenter proxies. Its residential plans can pick one Canadian city. Purchased traffic has no scheduled expiry date, so an unused balance simply waits.
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.