HProxy · Free Pakistan pool
Free Pakistan proxy list 2026
Pakistan's free proxies from our pool: a short list where most rows fail, but working ones last weeks.
PakistanAnonymousYou're viewing free Pakistani proxies. See the full list.
Browse the complete free proxy list: every country, protocol and anonymity grade, in one live view.
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.
Pakistan proxies right now, by the numbers
The pool currently holds 149 Pakistan proxies spread across 25 different networks. They respond in 6210ms at the median, much slower than the 3615ms median across the whole free pool. The busiest exits are Karachi, Lahore, Islamabad. 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 Pakistani 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 Pakistani proxies.
Pakistan's free list is short, and most of it does not work. The rows below are what our checker found there in the last two days.
At 22:56 UTC on 27 September 2026, only 18 of 142 Pakistani entries in rotation were passing. In the thirty minutes before, 72 of the 142 had been tested again.
Two hours later, at 01:06 UTC, our server in the United States tried all 28 live entries. Ten relayed a plain web request: six exited in Pakistan and four abroad.
Nearly half the list sits on one Connect Communication address, which never gave us a Pakistani exit. Its rows took no connection at 22:58 UTC, then relayed from other countries two hours later.
The few entries that do work tend to stay. Among Pakistani entries that answered and later stopped, half lasted 41 days or more, against 9.8 elsewhere. That median rests on only 74 entries, on addresses with fewer than 20 such entries. Neither median includes Amazon's networks or the faulty evening of 14 June.
No live Pakistani entry was graded transparent at that minute. Still, a free proxy encrypts nothing, and for steady work paid Pakistan proxies are the practical route.
01
Thirty-two live entries against the rest of the pool
The slice is small, so read each line below as a measurement of 32 entries, not a trend.
| Measured 28 September 2026 | Pakistan | Rest of the pool |
|---|---|---|
| Live entries measured | 32 | 4,046 |
| Median success rate across its own checks | 31.8% | 34.0% |
| Passed ten checks at 90 percent | 0.0% | 9.0% |
| Median latency from our server in the United States | 6,177 ms | 6,453 ms |
| Flagged as datacenter by our list | 25.0% | 21.0% |
Taken from our free pool at 14:49 UTC on 28 September. Busy addresses, 20 live entries or more, stay out of both columns.
Six of the eight datacenter entries sat on the one Connect Communication address. Every latency figure here comes from our server in the United States, so yours will differ.
02
Why the working Pakistani entries last a month
Our engine had set aside 584 Pakistani entries from ordinary addresses by 28 September. 518 of them never answered once, 88.7 percent, level with the rest of the pool.
79 Pakistani entries answered for a while and then stopped, and no address held 20 of them. 13 of the 74 counted sat on the Connect address; without them the median rises to 49 days.
Half were still answering after 41 days, and more than half lasted beyond thirty days.
| Measured 28 September 2026 | Pakistan | Rest of the pool |
|---|---|---|
| Worked, then stopped | 79 | 297,844 |
| Left out: on addresses with 20 or more | 0 | 261,669 |
| Left out: the evening of 14 June | 5 | 9,187 |
| Left out: other entries on Amazon's networks | 0 | 1,066 |
| Counted | 74 | 25,922 |
| Median lifespan of those counted | 41.2 days | 9.8 days |
| Of those counted, stopped within a day | 8.1% | 24.7% |
| Of those counted, lasted more than thirty days | 58.1% | 30.9% |
Read at 17:19 UTC; it skips addresses holding 20 or more such entries. The 14 June evening our checker failed, marking about 128,000 entries dead, is left out.
A quarter of the Pakistani entries timed here stopped within about nine days; elsewhere, within about a day. With 74 entries, one busy month could move these figures a long way.
03
Ten relays out of twenty-eight
Our server in the United States asked each live entry for two things. One was a page that reports the address it sees, the other Google over an encrypted connection.
| Measured 28 September 2026 | Entries |
|---|---|
| Tested | 28 |
| Did not accept a connection | 10 |
| Relayed the plain web request | 10 |
| Of those, exiting in Pakistan | 6 |
| Of those, leaving from the listed address | 4 |
| Opened Google over an encrypted connection | 7 |
| Certificate did not verify | 0 |
Run at 01:06 UTC from our server in the United States; ip-api.com placed each exit.
All six Pakistani exits came from rows that stand alone, three of them in Punjab. The four exits abroad all came through the Connect address: three in Tokyo, one in California.
The ten relays took a median of about 4.6 seconds. Eight more entries accepted a connection but relayed nothing.
04
Nearly half the list never exits in Pakistan
The list keeps any entry that answered in the past 48 hours: 135 rows on 64 addresses.
65 of the rows are ports 10900 to 11012 on one Connect Communication address. Our server in the United States tried all 65 at 22:58 UTC, and none accepted a connection.
Two hours later, 31 of the 65 relayed our request, every one from outside Pakistan. The exits spread over 12 countries, most often the United States and Japan.
The other 70 rows, on 63 addresses, gave 17 relays, all exiting in Pakistan, and no bad certificate.
| Measured 28 September 2026 | On the Connect address | Every other entry |
|---|---|---|
| Tested | 65 | 70 |
| Did not accept a connection | 28 | 29 |
| Relayed a plain web request | 31 | 17 |
| Of those, exiting in Pakistan | 0 | 17 |
| Of those, leaving from the listed address | 0 | 12 |
| Opened Google over an encrypted connection | 31 | 2 |
All 135 rows were tried at 01:07 UTC on 28 September, from our server in the United States.
For a Pakistani exit, skip that address's long run of rows and try rows that stand alone.
05
The Pakistani networks on the list
At 22:56 UTC on 27 September, Connect Communication carried 6 live entries, all on the address above. Nayatel carried 3, Multinet and Wateen Telecom 2 each, and five more networks one each.
The Pakistan Telecommunication Company, PTCL, carried a single live entry. Each operator name follows its record at APNIC, the internet registry for the Asia Pacific.
Lahore held 5 live entries, and Faisalabad, Islamabad and Karachi 2 each. Seven had no city on record, and a city is a database guess.
06
Trying a Pakistani entry
Take one row's address, port and protocol, and put all three into your browser or tool.
Of the 18 live on 27 September, 11 spoke SOCKS4, 8 HTTP, and 6 each HTTPS and SOCKS5.
Port 8080 carried 5 of them, and ports 4145 and 1080 two each.
Put the entry through our proxy checker before you rely on it: status, speed, anonymity, country and network.
Expect most rows to fail, and keep trying further down the list until one relays.
Questions
Frequently asked.
Only from the right rows. On 28 September 2026 our server in the United States tried all 28 live entries, and 10 relayed. By ip-api.com's reading, all six Pakistani exits came from rows that stand alone. The Connect address sent its four abroad.
On 28 September the median live entry took 6,177 ms from our checker in the United States. Pakistani entries were a shade quicker than the 6,453 ms measured on ordinary addresses elsewhere. The ten relays in our test took a median of about 4.6 seconds. Not one live Pakistani entry answered our checker within half a second.
Only for public pages. None of the 18 live entries was graded transparent that day, but a free entry adds no encryption. Its operator can read anything sent without HTTPS, and strangers can use it at the same time.
The working ones outlast most: a median 41 days, where the rest of our pool reached 9.8. That rests on 74 entries, counted only on addresses with fewer than 20 such entries. Amazon's networks and one June evening are not counted on either side. Most never work, though: 88.7 percent of those our engine set aside from ordinary addresses never answered.
SOCKS4 was the most common protocol on 27 September 2026, on 11 of the 18 live entries. Port 8080 carried 5 of them, more than any other port. Always use the exact port and protocol printed in the row.
Nearly half the rows sit on one address that never gave us a Pakistani exit. From our server in the United States, it first took no connection, then relayed from abroad. Of the other 70 rows on 28 September 2026, 29 took no connection. The list keeps a row for 48 hours after its last success, so many rows are already stale.
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.