The pool currently holds 250 Hong Kong proxies spread across 31 different networks. They respond in 1449ms at the median, quicker than the 2190ms median across the whole free pool. The busiest exits are Hong Kong, Kwai Chung, Kowloon Tong. These figures come straight from the live pool and move every few minutes as proxies are re-verified.

By protocol

HTTP52 HTTPS186 SOCKS47 SOCKS525

By anonymity

Elite216 Anonymous23 Transparent11

Biggest hosting networks

Amazon172 Alibaba17 Tencent6 UCloud6 Cloudie6 We Love4 Hong Kong4 YISU4

About

What our tests found on the Hong Kong 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.

Get the free app Check online IP lookup

The long read

About free Hong Kong proxies.

At 08:43 UTC on September 28, 2026, our pool held 68 live Hong Kong entries.

Nineteen sat on a single address, 202.181.24.102, and its relays all left from outside Hong Kong.

Four Amazon addresses carried another 97 rows of the 48-hour list, and none relayed in two passes.

The other 102 rows gave 23 relays in each pass; 43 of those 46 left from Hong Kong.

When a job needs a Hong Kong address every time, paid Hong Kong proxies are the surer choice.

Strong live figures, one busy address aside

Set against the pool's ordinary addresses at 11:22 UTC, the Hong Kong slice looks strong.

Live Hong Kong entries against the rest of the pool

Measured September 28, 2026	Hong Kong	Rest of the pool
Live entries measured	33	3,901
Median success rate across its own checks	68.6%	33.8%
Passed ten checks at 90 percent	24.2%	9.2%
Median latency from our server in the United States	3,392 ms	6,086 ms
Flagged as datacenter by our list	54.5%	21.2%

Read at 11:22 UTC, without the addresses that hold 20 or more live entries, in both columns.

Counting the 23 entries on 202.181.24.102 as well, the median success rate read 78.0 percent.

At 08:43, that address held 19 of the 32 SOCKS5 entries; elsewhere HTTP led, with 29.

Tencent and Alibaba carried six live entries each, UCloud five, and PCCW six over two networks.

One address, exits in Taipei, Tokyo and Singapore

Our database puts 202.181.24.102 on Cloudie's network, and APNIC registers its block to Converged Communications Limited.

At 08:44 UTC, our list carried 30 SOCKS5 rows on it, on ports 10801 to 10836.

Seventeen of them relayed, and every one left from a different address abroad.

ip-api placed seven exits in Taipei, five in Tokyo, four in Singapore and one in Oregon.

Chunghwa Telecom ran the Taipei exits; the rest sat on Amazon, by ip-api's reading.

In the live test, four of its 19 entries relayed: three through Taipei, one through Oregon.

By 09:24 UTC it carried 26 of the 70 live entries.

Its rows then relayed 29 times in our two tests, again never from Hong Kong.

The 17 ports that relayed more than once always kept the same exit city.

At 08:50, another free list carried six rows on the same address.

Amazon rows that relayed nothing

At 08:44 UTC, 97 list rows sat on four Amazon addresses, 69 of them on 18.163.182.106.

ARIN and APNIC register all four blocks to Amazon, and not one of the 97 rows relayed.

Most answered HTTP 400 or reset the connection, and 29 showed certificates that failed verification.

At 09:24, the same four addresses held 91 rows; none relayed, and 21 showed failed certificates.

Of all Hong Kong entries that worked and then stopped, 1,682 sat on 37 Amazon addresses.

At 08:50, another free list showed 18 Amazon rows among its first 20 for Hong Kong.

Where the relays came from

Our server fetched a page from ip-api.com through each row; that service names and places the arriving address.

Our test of the 48-hour list, without the 97 Amazon rows

Measured September 28, 2026	Cloudie address	Other rows
Rows tested	30	102
Did not accept a connection	1	31
Relayed the plain web request	17	23
Of those, exiting in Hong Kong	0	22
Certificate did not verify	0	1

Our server in the United States ran this at 08:44 UTC, and ip-api.com located each exit.

The 23 relays among the other rows took about 3.2 seconds at the median.

Twenty Hong Kong exits were the listed address itself; one more listed address sat in Japan.

In the live test, 20 of the 49 entries off 202.181.24.102 relayed, 18 in Hong Kong.

One listed address sits in Guangdong by ip-api's reading, and one Tencent row exited in Vietnam.

In our second pass, the other rows again gave 23 relays, 21 of them in Hong Kong.

That Tencent row reached ip-api from an address placed in Vietnam, and Cloudflare from one in Hong Kong.

A second row left from its listed address, which ip-api places in Amsterdam.

The live test found fewer this time: 11 of 44 entries off 202.181.24.102 relayed, 10 in Hong Kong.

Longer lives than the pool's

Four in five retired Hong Kong entries on ordinary addresses never passed a single check: 3,351 of 4,244.

Elsewhere in the pool the share is higher still, 88.8 percent.

Hong Kong entries that worked and then stopped, against the rest of the pool

Measured September 28, 2026	Hong Kong	Rest of the pool
Worked, then stopped	2,787	295,135
Left out: on addresses with 20 or more	1,859	259,809
Left out: the evening of June 14	129	9,063
Left out: other entries on Amazon's networks	21	1,045
Counted	778	25,218
Median lifespan of those counted	10.4 days	9.7 days
Of those counted, stopped within a day	19.8%	24.8%
Of those counted, lasted more than thirty days	23.3%	31.2%

Read at 17:19 UTC; one June evening, when our checker marked about 128,000 entries dead, is left out.

Fewer Hong Kong entries died within a day, 19.8 against 24.8 percent, though fewer passed a month.

Little filtering in OONI's counts

Across the month to September 28, OONI counted 117,913 web tests run from Hong Kong.

Of those, 95.2 percent loaded normally.

No site with 100 or more tests showed confirmed blocks above 0.70 percent of them.

Only 10 of 938 tests on Facebook came back other than normal, and 6 of 932 on YouTube.

Putting a Hong Kong row to work

If you need a Hong Kong exit, skip the rows on 202.181.24.102.

Skip rows on Amazon's 18.163, 18.166, 43.198 and 43.199 blocks as well; none relayed for us.

With those two groups aside, rows showing 50 percent uptime or more relayed about three times as often.

It was 16 of 42 against 7 of 60, in both passes.

Give a failing row a second try: most live rows that relayed did so once in two tests.

Off 202.181.24.102, that was 16 of 26 in the first pass and 14 of 20 in the second.

Ports 3128, 1080 and 80 carried the most live entries off 202.181.24.102.

Run a row through our proxy checker first; it reports speed, anonymity, country and network.

Questions

Frequently asked.

Every question

Usually, away from one address: off 202.181.24.102, 71 of 77 relays in four tests left from Hong Kong. That address relayed 50 times, never from Hong Kong.

Faster than most: at 11:22 UTC, live entries off the busy address answered in a median 3,392 ms. The pool's other ordinary entries needed 6,086 ms, measured from our server in the United States.

No. Five of the 68 live entries were transparent, so a site could see the address behind them. The Amazon rows showed 29, then 21, certificates that failed verification, and one Alibaba row a self-signed one.

Longer than most: the median entry we could time lasted 10.4 days, against 9.7 across the pool. Fewer died within a day too: 19.8 percent, against 24.8. The count skips addresses holding 20 or more such entries, Amazon's networks and one June evening.

Four Amazon addresses held 97 of the 229 list rows, then 91 of 223, and none relayed. Of the 102 other rows, 31 took no connection at all, then 33.

Few: 3 of the 68 live entries were placed in Kowloon, 1 in Kowloon Tong, and 29 nowhere. A location database supplies each town, so read it as an 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.

Clean residential poolsCity-level targetingSticky sessions up to 24 h

Starting from

$0.18/GB

Billed per GB · balance never expires

Get started free Compare plans & pricing

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.

Read the API docs Set up your assistant

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.

Add it to your assistant

CLI

The list from a terminal: hproxy list --country DE --limit 20, from the command line of the free HProxy app.

See the commands

API docs

The free list's API, documented end to end with real responses: the filters, the formats, the limits.

Read the docs

llms.txt

The whole documentation as markdown for any model that reads: /llms.txt for the index, /llms-full.txt for everything.

Open llms.txt

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.

The same live list, one thing at a time.

Free proxies by country

Hong Kong proxies right now, by the numbers