HProxy · Free Switzerland pool
Free Switzerland proxy list 2026
We tested every Swiss row of our free list twice. About half sit on Amazon and Zscaler addresses in Zurich.
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
Switzerland proxies right now, by the numbers
The pool currently holds 181 Switzerland proxies spread across 17 different networks. They respond in 1392ms at the median, much quicker than the 3998ms median across the whole free pool. The busiest exits are Zurich, Opfikon, Bellach. 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 Swiss 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 Swiss proxies.
On 28 September 2026 at 07:46 UTC, our pool counted just 14 live Swiss entries.
Of the 47 rows on the 48-hour list, 25 sat on Amazon and Zscaler addresses in Zurich.
Those 25 relayed nothing for us; the 22 other rows produced five relays, three inside Switzerland.
At 11:35 UTC, live Swiss entries passed a median 77.5 percent of our checks, against 33.9 elsewhere.
Still, 3 of the 14 were transparent and showed sites the address behind them. For an address that stays put, paid Switzerland proxies are the steadier route.
01
Fourteen live entries, thirteen networks
Below, the 8 Swiss entries live at 11:35 UTC sit beside the pool's ordinary addresses.
| Measured 28 September 2026 | Switzerland | Rest of the pool |
|---|---|---|
| Live entries measured | 8 | 3,897 |
| Median success rate across its own checks | 77.5% | 33.9% |
| Passed ten checks at 90 percent | 25.0% | 9.2% |
| Median latency from our server in the United States | 2,288 ms | 6,301 ms |
| Flagged as datacenter by our list | 62.5% | 22.9% |
Read at 11:35 UTC; neither column counts addresses that hold 20 or more live entries.
At 07:46, Zscaler carried two live entries, Datasource two over two networks, Swisscom and Sunrise one each.
Zurich held 4 of the 14, five had no town on record, and Bern and Basel had none.
02
Amazon and Zscaler rows in Zurich
At 07:47 UTC, three Amazon addresses in Zurich held 18 list rows, and three Zscaler addresses 7.
Our database places the six on Amazon's and Zscaler's networks; RIPE and ARIN confirm both owners.
None of the 25 relayed: the Amazon rows answered with errors, and most Zscaler rows timed out.
The Amazon rows also showed 17 certificates that failed verification.
In our second pass, the same six addresses carried 20 rows, and not one relayed.
Our engine had already set aside 1,441 working entries on ten Amazon and nine Zscaler addresses there.
At 07:51, another free list showed 20 Swiss rows on its first page, each on Amazon or Zscaler.
03
Three live relays, one placed in Germany
Our server asked ip-api.com, through each live row, which address arrived and where that address sits.
| Measured 28 September 2026 | Entries |
|---|---|
| Tested | 14 |
| Did not accept a connection | 6 |
| Relayed the plain web request | 3 |
| Of those, exiting in Switzerland | 2 |
| Of those, leaving from the listed address | 3 |
| Opened Google over an encrypted connection | 2 |
| Certificate did not verify | 0 |
Started at 07:46 UTC on our United States server, with ip-api.com placing each exit.
The three relays needed about 2.9 seconds at the median, and five rows connected without relaying.
One relay, on the GCS network, left from its listed address, which ip-api places in Frankfurt.
The 22 other list rows gave 5 relays: three in Switzerland, one in Frankfurt, one in Luxembourg.
For the Luxembourg row, Cloudflare's own trace placed the same exit in Switzerland.
Thirty-nine minutes on, 4 of 11 live entries relayed, every one from its listed address in Switzerland.
In the second list test, the 22 rows outside Amazon and Zscaler relayed four times, always inside Switzerland.
04
Shorter lives than the pool's
Most retired Swiss entries on ordinary addresses never worked: 505 of 613, or 82.4 percent.
Across the rest of the pool that share is 88.6 percent.
| Measured 28 September 2026 | Switzerland | Rest of the pool |
|---|---|---|
| Worked, then stopped | 1,585 | 296,837 |
| Left out: on addresses with 20 or more | 1,446 | 260,673 |
| Left out: the evening of 14 June | 32 | 9,159 |
| Left out: other entries on Amazon's networks | 2 | 1,073 |
| Counted | 105 | 25,932 |
| Median lifespan of those counted | 6.3 days | 9.8 days |
| Of those counted, stopped within a day | 27.6% | 24.7% |
| Of those counted, lasted more than thirty days | 35.2% | 31.0% |
Read at 20:53 UTC; about 128,000 entries marked dead at once when our checker failed are left out.
Two busy Zscaler addresses hold 27 of the 105; without them the median is 3.5 days.
05
Thin filtering on Swiss networks
OONI logged 400,262 web tests from Switzerland in the month to 28 September; 95.7 percent loaded normally.
Confirmed blocks were thin: the highest share on any site with 100 or more tests was 1.96 percent.
Of 3,393 tests on YouTube, 3,315 came back normal.
06
Putting a Swiss row to work
Skip rows on Amazon's 16.18, 16.62 to 16.63 and 51.34 blocks and on Zscaler's 147.161 and 165.225 addresses.
Rows showing 50 percent uptime or higher relayed three times as often or more, in both passes.
That leaves the Amazon and Zscaler rows aside; one Amazon row showed 96 percent and relayed nothing.
Port 80 served three live entries, and 3128 and 8080 two each.
Check a row's speed, anonymity and country in our proxy checker before trusting it.
Questions
Frequently asked.
Mostly: our four tests saw 16 relays, and 13 of them left from inside Switzerland. The other three left from their listed addresses, which ip-api places in Germany or Luxembourg.
Quick: at 11:35 UTC, half the live Swiss entries answered our US server within 2,288 ms. Entries on the pool's ordinary addresses took 6,301 ms, nearly three times as long.
Not for anything private: 3 of the 14 live entries were transparent. The Amazon rows also showed 17 certificates that failed verification, then 12.
A median 6.3 days for the 105 Swiss entries we could time, against 9.8 for the rest. Neither count includes Amazon's networks, one June evening or any address holding 20 or more such entries. Set aside two busy Zscaler addresses as well and it falls to 3.5 days.
About half the 48-hour list sat on Amazon and Zscaler in Zurich, which relayed nothing in 45 tries. The 22 rows elsewhere gave five relays, then four, all but two inside Switzerland.
Zurich held 4 of the 14 live entries and Geneva 1; five had no town on record. Towns come from a location database and are estimates.
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.