HProxy · Free Nepal pool
Free Nepal proxy list 2026
Every proxy below sits on an address in Nepal, re-checked on a rolling cycle. The numbers on this page come from our own checker, measured on 15 September 2026.
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.
Nepal proxies right now, by the numbers
The pool currently holds 38 Nepal proxies spread across 13 different networks. They respond in 7067ms at the median, quicker than the 8703ms median across the whole free pool. The busiest exits are Kathmandu, Patan, Birendranagar. These figures come straight from the live pool and move every few minutes as proxies are re-verified.
By anonymity
About
About these free Nepal proxies
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 checker and see which proxies are alive, fast and anonymous right now.
The long read
About free Nepal proxies.
The list above holds every free proxy in Nepal that answered our checker recently. Copy an address and port, and sites you open will see an address in Nepal.
At 09:10 UTC on 15 September 2026, 7 entries in Nepal were alive. 38 were in rotation, and 38 of those had been checked in the previous thirty minutes.
Only 7 entries in Nepal were alive, too few for a fair success rate.
Entries in Nepal that stopped answering lived a median 72.4 hours, about 3 days. That is shorter than the whole pool's median of 144.6 hours. 17.1 percent died inside their first hour, and 7.1 percent lasted more than thirty days.
Being alive at the last check does not make an address usable. All 7 live entries were flagged for recent abuse, and 1 sat on datacenter space. For work that has to keep running, paid Nepal proxies are built for it.
01
Nepal against the whole free pool
The table compares Nepal with the whole free pool, from the same read-only query.
| Measured 15 September 2026 | Nepal | Whole pool |
|---|---|---|
| Live entries measured | 7 | 5,822 |
| Median lifespan of entries that died | 72.4 hours | 144.6 hours |
| Died inside the first hour | 17.1% | 21.3% |
| Classed as datacenter | 14.3% | 58.0% |
| Flagged for recent abuse | 100.0% | 97.9% |
HProxy free pool, queried read-only at 09:10 UTC on 15 September 2026. Lifespans cover every entry that died since the pool opened in May 2026.
02
Protocols and grades in Nepal
SOCKS4 was the most common protocol, spoken by 5 of the 7 live entries. 7 of them were graded elite, so sites saw neither your address nor a proxy header.
Among the 115 countries with live entries, Nepal held the 50th largest number. Since May 2026 our checker has recorded 248 entries on 217 addresses in Nepal.
| Measured 15 September 2026 | Live entries |
|---|---|
| Speaks HTTP | 0 |
| Speaks HTTPS | 1 |
| Speaks SOCKS4 | 5 |
| Speaks SOCKS5 | 1 |
| Graded elite | 7 |
| Graded anonymous | 0 |
| Graded transparent | 0 |
| All live Nepal entries | 7 |
HProxy free pool, queried read-only at 09:10 UTC on 15 September 2026. One entry can speak more than one protocol, so those rows can add up to more than the total.
03
What a free Nepal proxy can reach
We tested all 38 listed entries on 15 September 2026, each one through the entry itself. Each one fetched Cloudflare's trace page over plain HTTP and over TLS, then Google's connectivity check.
| Tested 15 September 2026 | Entries |
|---|---|
| Tested | 38 |
| Did not accept a connection | 22 |
| Completed at least one request | 3 |
| Carried encrypted traffic | 0 |
| Opened Google | 0 |
| Certificate did not verify | 0 |
| Showed an exit address | 3 |
| Of those, exiting in Nepal | 3 |
HProxy test from one server in Germany. Exit countries from Cloudflare's own trace.
None of the tested entries carried encrypted traffic to the end.
04
Who runs the networks behind these proxies
Most live entries in Nepal sit on internet provider networks, not in data centers. The names below are the network names our address data records for each AS number.
| Network | AS number | Live entries | Classed as datacenter |
|---|---|---|---|
| WorldLink Communications | AS17501 | 2 | 1 |
| Subisu Cablenet | AS4007 | 1 | 0 |
| Nepal Telecommunications Corporation | AS23752 | 1 | 0 |
| Websurfer Nepal Communication System Pvt. Ltd | AS24550 | 1 | 0 |
| BroadLink Networks and Communications | AS55427 | 1 | 0 |
| Techminds Network Pvt. Ltd. | AS58504 | 1 | 0 |
| All live Nepal entries | All networks | 7 | 1 |
HProxy free pool, live set at 09:10 UTC on 15 September 2026.
05
How to use a free Nepal proxy
Pick a row and note its address, port and protocol before you set it in your tool. HTTP and HTTPS entries suit browsers and scrapers, while SOCKS5 entries also carry traffic from other tools.
Take several entries and rotate between them, because a free entry can drop between two checks. A free SOCKS5 entry adds no encryption of its own, so never send a password through one.
Questions
Frequently asked.
Yes, every entry on this page is free to copy and use, with no signup. They are public and shared, so test one right before you rely on it.
Treat them as public, because whoever runs the server can read any traffic that is not encrypted. On 15 September 2026, all 7 live entries were flagged for recent abuse.
For work that has to keep running, HProxy sells Nepal proxies with city targeting. They are pay as you go with no subscription, and the balance never expires.
Not long: entries in Nepal that died lived a median 72.4 hours. 17.1 percent died inside their first hour, and the whole pool's median is 144.6 hours.
On 15 September 2026 the largest networks were WorldLink, Subisu Cablenet and Nepal. 14.3 percent of live entries were classed as datacenter.
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 Code, Cursor, Windsurf 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: the free proxy list, the checker and the IP lookup as tools in Claude Code, Claude Desktop, Cursor, Windsurf or anything on stdio. No key, no account.
CLI
The list from a terminal: npx hproxy-mcp list --country de --limit 20. One line, nothing to install.
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.
claude mcp add hproxy -- npx -y hproxy-mcpCursor, Claude Desktop, Windsurf and Cline take the same server as {"command": "npx", "args": ["-y", "hproxy-mcp"]}. This page's tool is proxy_list. - Command line
- The same tool without an assistant. Prints JSON, so it pipes.
npx hproxy-mcp list --country de --protocol socks5 --limit 20 - 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: install it with npx -y hproxy-mcp and use the proxy_list tool. 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.