HProxy · Free Vietnam pool
Free Vietnam proxy list 2026
Vietnamese free proxies from our own pool, each row showing uptime, speed and the network it sits on. In our latest live test, all 25 entries that relayed a request exited inside Vietnam.
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.
Vietnam proxies right now, by the numbers
The pool currently holds 378 Vietnam proxies spread across 28 different networks. They respond in 4482ms at the median, slower than the 3451ms median across the whole free pool. The busiest exits are Ho Chi Minh City, Hanoi, Bac Ninh. 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 we found testing the Vietnamese 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 Vietnamese proxies.
This list gathers the free proxies in Vietnam that answered our checker in the last two days. When a row works, sites almost always see a Vietnamese address. All 25 live relays in our latest test exited there.
When we looked, at 20:57 UTC on 27 September 2026, 75 Vietnamese entries were alive out of 256. Our checker had looked at 111 of those 256 within the previous half hour.
By 01:37 UTC, nearly five hours on, the live count had grown to 91. We pushed one plain web request through each, from our server in the United States. 37 took no connection, 25 relayed it, and ip-api.com put all 25 exits in Vietnam. 14 of them left from the address the list gives.
Just 3 of the 75 carried our datacenter flag, a fifth of the share on ordinary addresses elsewhere. The rest sit on Vietnamese carriers such as CMC Telecom, VNPT, Viettel and FPT Telecom.
At 13:53 UTC the next day, Vietnamese entries on ordinary addresses passed a median 42.5 percent of checks. Elsewhere on ordinary addresses the median success rate was 33.7 percent. Eight of their 59 had passed ten checks at 90 percent, against 8.4 percent elsewhere. Among entries that worked and then stopped, the Vietnamese median was 2.1 days, where the rest reached 10.4. Both skip addresses holding 20 or more such entries, and also Amazon's networks and a faulty June evening.
14 of the 75 live entries were graded transparent: they hand the site your real address. A job that has to run from Vietnam every day belongs on paid Vietnam proxies.
01
Five numbers from one minute of our pool
These five lines come from the next day, 28 September, at 13:53 UTC.
| Measured 28 September 2026 | Vietnam | Rest of the pool |
|---|---|---|
| Live entries measured | 59 | 4,291 |
| Median success rate across its own checks | 42.5% | 33.7% |
| Passed ten checks at 90 percent | 13.6% | 8.4% |
| Median latency from our server in the United States | 5,985 ms | 6,414 ms |
| Flagged as datacenter by our list | 5.1% | 21.6% |
Busy addresses stay out of both columns; in Vietnam that is the CMC gateway, with 26 live entries.
The datacenter line still stands out: 5.1 percent here against 21.6 percent elsewhere.
With the gateway's 26 entries back in, the Vietnamese median falls to 33.1 percent.
Latency is timed from our server in the United States, and yours will not match it.
02
Two days: how long a working Vietnamese proxy lasts
8,349 of the 9,257 Vietnamese entries our engine retired from ordinary addresses never answered even once. That is 90.2 percent, close to the 88.6 found across ordinary addresses elsewhere.
1,486 Vietnamese entries did work for a while. 337 of them sat on 9 busy addresses in Vietnam and are not timed.
Each entry is timed from our first sighting to the moment it went silent.
| Measured 28 September 2026 | Vietnam | Rest of the pool |
|---|---|---|
| Worked, then stopped | 1,486 | 296,437 |
| Left out: on addresses with 20 or more | 337 | 261,332 |
| Left out: the evening of 14 June | 221 | 8,971 |
| Left out: other entries on Amazon's networks | 0 | 1,066 |
| Counted | 928 | 25,068 |
| Median lifespan of those counted | 2.1 days | 10.4 days |
| Of those counted, stopped within a day | 31.5% | 24.4% |
| Of those counted, lasted more than thirty days | 7.0% | 31.8% |
These figures date from our read at 17:19 UTC on 28 September 2026. The 14 June evening, when a checker fault marked some 128,000 entries dead, is left out. An address is left out once 20 of its entries have worked and then stopped.
Vietnamese entries drop out fast: 31.5 percent were gone within a day, against 24.4 elsewhere. Only 7.0 percent passed thirty days, against 31.8 percent.
03
Where the 25 relays came out
Our server in the United States asked each live entry to fetch a page echoing its address. Then it asked each entry to reach Google through an encrypted tunnel.
| Measured 28 September 2026 | Entries |
|---|---|
| Tested | 91 |
| Did not accept a connection | 37 |
| Relayed the plain web request | 25 |
| Of those, exiting in Vietnam | 25 |
| Of those, leaving from the listed address | 14 |
| Opened Google over an encrypted connection | 23 |
| Certificate did not verify | 0 |
Our test at 01:37 UTC, from one server in the United States; ip-api.com named the exit countries.
The middle relay time was about 3.3 seconds. Hanoi held 10 of the exits and Ho Chi Minh City 9.
04
One gateway holds more than a third of the list
The list shows every entry that answered within 48 hours: 248 at 01:37 UTC. 93 of them share one CMC Telecom address in Ho Chi Minh City, on ports 10000 to 10251.
26 of the 91 live entries were among those ports. We tested all 248 entries. From our server in the United States, 8 of the 93 relayed a request. Each came out through another CMC Telecom address in Vietnam, never the listed one.
A gateway works that way: it takes your connection on one address and sends it out from another. Not one of the 248 showed a certificate that failed to verify.
| Measured 28 September 2026 | On the CMC address | Every other entry |
|---|---|---|
| Tested | 93 | 155 |
| Did not accept a connection | 51 | 90 |
| Relayed a plain web request | 8 | 28 |
| Of those, exiting in Vietnam | 8 | 28 |
| Of those, leaving from the listed address | 0 | 21 |
| Opened Google over an encrypted connection | 5 | 25 |
Our test of all 248 at 01:38 UTC, from our server in the United States. Every relay exited in Vietnam; in our first test, the day before, one did not.
05
The carriers behind the Vietnamese rows
Of the 75 live at 20:57 UTC, CMC Telecom carried 22, every one on the gateway address above. VNPT followed with 10, Viettel and a second VNPT network with 8 each, and FPT Telecom with 5. APNIC, the registry for the Asia Pacific, supplied every operator name above.
Of those 75, Ho Chi Minh City had 42 and Hanoi 15; 15 had no city on record. A city is an estimate from a database, nothing firmer.
06
Putting a Vietnamese row to work
Read the address, port and protocol off one row and paste them into your tool's settings.
Protocol counts for the 75 live at 20:57 UTC: HTTP 51, HTTPS 23, SOCKS4 10, SOCKS5 8. They add up to more than 75 because one entry can speak several.
Away from the gateway, SOCKS rows relayed 10 of 18 live and 15 of 51 on the list. HTTP and HTTPS rows managed only 13 of 47 and 13 of 104. So start with a SOCKS row when one is on the list.
Among those 75, port 8080 answered for 12, and 3128 and 1080 for 7 each.
Check a row in our proxy checker first; it reports status, speed, anonymity, country and network.
Keep a few rows in reserve: half the entries timed above were gone within about two days.
Questions
Frequently asked.
Almost always, in tests sent from our server in the United States. On 28 September 2026, all 25 live entries that relayed our request exited in Vietnam. Their countries come from ip-api.com, and 14 of the 25 left from the listed address. The day before, one list relay exited in Germany.
A little faster than the rest of our free pool, and still slow. On 28 September, entries off the gateway took a median 5,985 ms from our US checker. The rest of the pool, busy addresses aside, took a median 6,414 ms. None of the 85 live entries came in under half a second.
For public pages only. On 27 September 2026, 14 of the 75 live entries were transparent, passing on the user's real address. Whoever operates an entry sees everything you send without HTTPS, so keep logins and payments away from it.
Not long: a median 2.1 days from our first sighting until the entry went quiet. Measured the same way, the rest of our pool reached 10.4 days. Addresses carrying 20 or more such entries sit outside both figures. Amazon's networks and one June evening do too. And most entries never work: 90 percent of those retired from ordinary Vietnamese addresses never answered.
8080 most often: 12 of the 75 live entries on 27 September 2026. Ports 3128 and 1080 came next with 7 each; the CMC gateway sits on ports from 10000 up.
No login at all, which is why strangers can share the same entry at the same moment. Paid proxies come with credentials that belong to you alone.
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.