HProxy · Free Singapore pool
Free Singapore proxy list 2026
This list holds only Singapore entries that answered our checker within the past 48 hours. The live rows are steadier than most, but five Amazon addresses relayed almost nothing.
SingaporeTransparentSingaporeTransparentSingaporeTransparentSingaporeTransparentSingaporeTransparentSingaporeTransparentSingaporeTransparentYou're viewing free Singapore 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.
Singapore proxies right now, by the numbers
The pool currently holds 324 Singapore proxies spread across 25 different networks. They respond in 2524ms at the median, quicker than the 3451ms median across the whole free pool. The busiest exits are Singapore, Loyang, Jurong Town. These figures come straight from the live pool and move every few minutes as proxies are re-verified.
By anonymity
About
Singapore's free list, measured row by row
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 Singapore proxies.
Singapore's free list is short, and its live rows are steadier than most. At 06:00 UTC on 28 September 2026, 63 Singapore entries were live in a pool of 19,370.
Those 63 passed a median 62.6 percent of their checks; the rest of the pool managed 33.5. Twelve of them passed ten checks at 90 percent, about twice the pool's share.
Of the 180 rows on the 48-hour list, 56 were on just five Amazon addresses. Only one of those 56 relayed our test request, from its own address in Singapore. When our server asked those rows for Cloudflare, 41 presented a certificate it would not accept.
Away from Amazon, 124 rows relayed a plain web request 22 times, 20 of them from Singapore. Another 16 opened an encrypted site while refusing or dropping that plain request.
Most live rows sit on cloud networks: DigitalOcean held 22, Alibaba and Tencent 6 each. Akamai and Oracle had 5 each, and only one sat on Singtel. Work that has to stay on a Singapore address for days is better served by paid Singapore proxies.
01
Singapore next to the rest of the free pool
No crowded address decides a row here: each one holding 20 or more entries is left out.
| Measured 28 September 2026 | Singapore | Rest of the pool |
|---|---|---|
| Live entries measured | 63 | 3,857 |
| Median success rate across its own checks | 62.6% | 33.5% |
| Passed ten checks at 90 percent | 19.0% | 9.3% |
| Median latency from our server in the United States | 4,146 ms | 6,071 ms |
| Answered in under one second | 11.1% | 7.8% |
| Retired entries that never answered once | 54.1% | 90.0% |
| Median lifespan of entries that died | 116 hours | 238 hours |
| Died within a day | 28.7% | 24.6% |
| Lasted more than 30 days | 22.4% | 31.2% |
Live Singapore figures come from 06:00 UTC and every lifespan from 17:17. The rest column's live figures and both retired shares come from 11:03 UTC. Lifespans cover entries that answered and later stopped, counted only on addresses holding fewer than 20 of them. They leave out Amazon's networks and one evening in June when our checker recorded 128,000 entries dead.
So a working Singapore entry lasted about five days, half the pool's median. The live ones answered quickly, though: 4.1 seconds at the median, against 6.1 elsewhere.
02
Five Amazon addresses and the other rows
At 06:00 UTC our server tried all 180 rows. Where a row let us connect, we fetched three things through it: an address echo, Cloudflare and Google.
| Tested at 06:00 UTC, 28 September 2026 | On 5 Amazon addresses | On 109 other addresses |
|---|---|---|
| Rows on the list | 56 | 124 |
| Passed their latest check | 1 | 62 |
| Did not accept a connection | 0 | 45 |
| Completed at least one request | 2 | 38 |
| Relayed our plain echo request | 1 | 22 |
| Came out in Singapore, by the echo | 1 | 20 |
| Opened Google | 1 | 15 |
| Failed a certificate check | 41 | 1 |
All tests ran from one HProxy server in the United States, and ip-api.com located each exit.
Three Amazon addresses carried 54 of the 56 rows. Only one of the 56 had passed its latest check.
At 06:05 UTC a certificate probe revisited 30 Amazon rows; 26 completed the encrypted handshake. Every one of those certificates claimed to be www.cloudflare.com, and none passed our server's check. Their issuers carried names such as gitlab, JFrog Artifactory and lab-computer-4186-9152.
Eight of them named a public authority. Four could be tested against a key we proved genuine, and every signature failed. Three named ZeroSSL and stopped letting us through before we could test them. The last named a Microsoft root whose key we could not prove.
A plain page request got the reply "Could not connect" from all 30, under 26 different server names. Nothing tells us who runs these addresses; their answers look more like a honeypot's than a proxy's. In NIST's words, a honeypot is designed to be attractive to potential crackers and intruders.
03
Encrypted sites worked where plain pages failed
Our first request through each row fetched a plain http:// page. Sixteen rows off Amazon refused or dropped it, yet opened Cloudflare or Google over an encrypted connection.
Nine of them answered the plain request with an error, code 403 or 405. Eleven of the sixteen sat on DigitalOcean addresses, and Cloudflare placed 15 in Singapore. The second test, an hour later, found 21 rows that behaved the same way.
04
Where the Singapore relays came out
Cloudflare answered through 23 rows, and 21 of those answers came from its Singapore data center.
The other two carried the code T1, which Cloudflare uses for Tor traffic. One came through a row on a Google address, and its echo exited in Germany.
A row our list showed without a town relayed from its own address, which ip-api.com placed in Amsterdam. The Tor Project's check answered through 7 of the 23 relays, and none of those was Tor.
05
How to use a free Singapore proxy
Skip rows on the Amazon addresses 54.255.249.161, 47.129.105.10 and 18.142.95.213; one relay came from 56 Amazon rows.
Off Amazon, a row whose Uptime reads 50 percent or more relayed about twice as often, both times. In the first test, 15 of 59 such rows relayed, against 7 of the other 65.
Test a row with an https:// page; in both tests, rows refused plain pages yet carried encrypted ones.
Only 5 of the 63 live entries spoke SOCKS5, and none of those adds encryption.
Fourteen of the 63 live entries were transparent and forward your real address with every request. The owner of a free row sees everything you send without HTTPS; keep logins and payments elsewhere.
Questions
Frequently asked.
They cost nothing, and there is no account to create. Other people share the same rows, so test one right before you use it.
Five Amazon addresses carried 56 of the 180 rows, and they relayed once. Tested from our server in the United States, 45 of the other 124 took no connection.
Quick for free rows: our checker in the United States timed the median live one at 4,146 ms. The rest of the pool, busy addresses left out, needed 6,071 ms. Relays in our test took 9.6 seconds at the median.
Mostly cloud: on 28 September DigitalOcean held 22 of the 63 live entries, Singtel just one.
HProxy sells Singapore residential proxies and dedicated Singapore IPs, paid as you go with no subscription. Purchased traffic has no scheduled expiry date, which suits work that comes in bursts.
Most working ones did: 21 of the 23 that relayed our echo exited in Singapore. One came out in Amsterdam and one in Germany. Every one of those requests left our server in the United States on 28 September 2026.
No: assume a stranger runs every row, and nothing sent without HTTPS is private. In our test, 41 Amazon rows answered with certificates our server rejected, and 14 live entries were transparent.
Not long: entries that worked and then stopped lasted a median 116 hours, against 238 elsewhere. The count skips busy addresses, Amazon's networks and one evening in June when our checker failed.
Treat the town beside a row as a guess from a geolocation database. Thirteen live rows even paired a Singapore town with a region such as Colorado or Texas.
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.