HProxy · Free Indonesia pool
Free Indonesia proxy list 2026
Free proxies that our checker places in Indonesia, each shown with its uptime, speed and network. In both our tests, every entry that relayed a request came out in Indonesia.
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.
Indonesia proxies right now, by the numbers
The pool currently holds 500 Indonesia proxies spread across 243 different networks. They respond in 4556ms at the median, much slower than the 2137ms median across the whole free pool. The busiest exits are Jakarta, Bekasi, Surabaya. 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 Indonesian 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 Indonesian proxies.
The rows below are free proxies on Indonesian addresses, taken from our own pool and re-tested all day. A working row shows sites an Indonesian address: all 101 that relayed in our latest test exited there.
At 20:02 UTC on September 27, 2026, our pool query found 1,093 of 3,864 Indonesian entries passing. Within the previous half hour, 1,974 of the 3,864 had been checked. Live counts move by the minute, so our test five and a half hours later started from 1,074.
From our server in the United States, 754 of the 1,074 did not even take a connection. Of the 101 that relayed a plain web request, 65 left from the listed address itself.
Only 6.5 percent of live Indonesian entries carried our datacenter flag, against a quarter elsewhere on ordinary addresses. The entries without the flag sat on 418 networks, 395 of them under Indonesian company names.
Indonesian entries fail more checks, yet the ones that work keep working. At 14:18 UTC on September 28, a live entry passed a median 28.3 percent of its checks. Entries on ordinary addresses elsewhere managed 37.8. Among those that worked and then stopped, the median Indonesian entry lasted 32 days, against 8 elsewhere. Each median leaves out addresses holding 20 or more such entries. Amazon's networks and one faulty June evening stay out as well.
320 of the 1,093 live entries were graded transparent, which means the site still sees your own address. For a job that must keep running from Indonesia, choose paid Indonesia proxies.
01
How the live Indonesian entries measure up
Indonesia's five lines were read again at 14:18 UTC on September 28.
| Measured September 28, 2026 | Indonesia | Rest of the pool |
|---|---|---|
| Live entries measured | 1,098 | 3,197 |
| Median success rate across its own checks | 28.3% | 37.8% |
| Passed ten checks at 90 percent | 0.1% | 11.5% |
| Median latency from our server in the United States | 7,553 ms | 5,911 ms |
| Flagged as datacenter by our list | 5.8% | 26.6% |
The rest column counts only addresses with fewer than 20 live entries; no Indonesian address had that many.
Of the five lines, the datacenter share says most about where these entries run. Speed here is the trip from our server in the United States, so yours will differ. Against the pool's ordinary entries, Indonesian rows were slower, and none answered within half a second.
02
How long a working Indonesian proxy keeps going
Most entries never work: of 16,480 Indonesian entries our engine retired from ordinary addresses, 13,505 never answered. Across the rest of the pool, entries on ordinary addresses did even worse: 89.0 percent never answered.
4,042 worked for a while, and 1,067 of those sat on 17 cloud addresses at Amazon and Alibaba. Each of those addresses held 20 or more, so none of them is timed.
A lifespan runs from the day we first saw an entry to the day it stopped answering.
| Measured September 28, 2026 | Indonesia | Rest of the pool |
|---|---|---|
| Worked, then stopped | 4,043 | 293,880 |
| Left out: on addresses with 20 or more | 1,067 | 260,602 |
| Left out: the evening of June 14 | 400 | 8,792 |
| Left out: other entries on Amazon's networks | 25 | 1,041 |
| Counted | 2,551 | 23,445 |
| Median lifespan of those counted | 31.6 days | 7.9 days |
| Of those counted, stopped within a day | 6.0% | 26.7% |
| Of those counted, lasted more than thirty days | 51.2% | 28.7% |
Read at 17:19 UTC on September 28, without busy addresses or Amazon's networks. It also skips June 14's evening, when a checker fault marked some 128,000 entries dead.
Early failures are rare here: 6.0 percent stopped within a day, against 26.7 percent elsewhere. A quarter were gone within ten days; the rest of the pool lost a quarter in under one.
03
What happened when we sent a request through each one
Each of the 1,074 live entries got two requests from our server in the United States. One asked for a page reporting the address it sees, the other for Google over an encrypted link.
| Measured September 28, 2026 | Entries |
|---|---|
| Tested | 1,074 |
| Did not accept a connection | 754 |
| Relayed the plain web request | 101 |
| Of those, exiting in Indonesia | 101 |
| Of those, leaving from the listed address | 65 |
| Opened Google over an encrypted connection | 71 |
| Certificate did not verify | 0 |
At 01:36 UTC our server in the United States tested all 1,074, and ip-api.com located the exits.
Through the 101 relays, the plain request took a median 5,938 ms. West Java held 24 of the exits, Jakarta 17 and East Java 16; no certificate failed.
04
Three addresses that fill rows without relaying anything
Our list keeps every entry that answered within 48 hours: 3,763 at 01:36 UTC on September 28.
65 of those rows sat on three Amazon addresses in Jakarta, 18 to 25 ports each. They were the same three as the day before. We tested all 65 from our server in the United States, and not one relayed a request. Asked for www.cloudflare.com, 24 of them answered with a certificate that did not verify.
For comparison, we drew a random 400 from the other entries: 22 relayed, all exiting in Indonesia. None of the 400 failed a certificate check, so the three busy addresses are the ones to avoid. Whatever the row, send nothing through an entry whose certificate fails to verify.
| Measured September 28, 2026 | On 3 busy Amazon addresses | A random 400 of the others |
|---|---|---|
| Tested | 65 | 400 |
| Did not accept a connection | 22 | 322 |
| Relayed a plain web request | 0 | 22 |
| Of those, exiting in Indonesia | 0 | 22 |
| Certificate did not verify | 24 | 0 |
| Opened Google over an encrypted connection | 0 | 9 |
Our server in the United States ran this list test at 01:44 UTC on September 28, 2026. The 400 were a random draw from the 3,698 entries on other addresses.
05
Who runs the networks behind the list
Telkom Indonesia carried the most live entries, 24, and Lintas Data Prima came next with 22. Most networks were tiny: 349 of the 429 held three entries or fewer.
12 live entries sat on the networks of eight local government offices, and 4 on four universities. Every operator name here is the one APNIC, the registry for the Asia Pacific, has on record.
Jakarta held 118 live entries, then Bekasi 42, Bandung 21 and Karawang 16. For 462 there was no city on record, and every city is a database's estimate.
06
An Indonesian exit and Indonesian filtering
An Indonesian entry sends traffic out through an Indonesian network, so local filtering can apply.
OONI is a volunteer project that measures internet censorship. Its volunteers tested vimeo.com from Indonesia 5,613 times in the month to September 27. 1,614 of those tests were confirmed blocked, and 2,599 loaded normally.
07
Using a free Indonesian proxy, step by step
Copy the address, port and protocol of one row, then enter them in your tool's proxy settings.
HTTP led on September 27, spoken by 694 live entries. HTTPS followed with 574, SOCKS4 had 57, and SOCKS5 just 2.
Pick a SOCKS row if one is listed. Live, 35 of 77 SOCKS rows relayed; of 997 HTTP and HTTPS rows, just 66 did. The random 400 agreed: 4 of 14 SOCKS rows against 18 of 386 others.
Port 8080 carried 430 of them, far ahead of 3125 with 194 and 1111 with 60.
Run the entry through our proxy checker first, and it will report status, speed, anonymity, country and network.
Keep spare rows ready: only 1 of the 1,093 live entries passed ten checks at 90 percent.
Questions
Frequently asked.
When it works, yes: all 101 live entries that relayed our request exited in Indonesia, by ip-api.com's reading. We sent it on September 28, 2026, from our server in the United States. 65 of the 101 left from the listed address, and most of the 1,074 tested relayed nothing.
Slow for real work, and slower than the pool's ordinary entries. On September 28 our US checker timed them at a median 7,553 ms. Entries on ordinary addresses elsewhere took 5,911 ms. Not one of the 1,098 live entries answered within half a second.
Not for anything private. On September 27, 2026, 320 of the 1,093 live entries showed the site the user's own address. On September 28, 24 list entries we tested showed certificates that failed, all on Amazon. Anyone operating the entry can read what you send without HTTPS, so never log in through one.
Longer than most: a median 32 days from our first sighting to its last answer. Across the rest of our pool, the same count gives 8 days. Addresses holding 20 or more such entries are left out of both. Amazon's networks are left out too, with one faulty evening in June. The catch: 81.9 percent of those retired from ordinary Indonesian addresses never answered once.
Use the port and protocol printed in the row, exactly as shown. On September 27, 2026, port 8080 carried 430 of the 1,093 live entries, and 3125 carried 194. HTTP was the protocol most of them spoke, 694 in all.
No, they take no login at all, so strangers can use the same entry while you do. A paid proxy comes with a username and password that only you hold.
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 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.