HProxy · Free Philippines pool
Free Philippines proxy list 2026
Free proxies on Philippine addresses from our own pool, nearly all on local phone and internet providers. Every entry that relayed a request in our tests exited in the Philippines.
PhilippinesAnonymousPhilippinesAnonymousYou're viewing free Philippine 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.
Free proxies by country
24 pages
Philippines proxies right now, by the numbers
The pool currently holds 438 Philippines proxies spread across 29 different networks. They respond in 5988ms at the median, much slower than the 2254ms median across the whole free pool. The busiest exits are Manila, Davao City, Cagayan de Oro. These figures come straight from the live pool and move every few minutes as proxies are re-verified.
By anonymity
Biggest hosting networks
About
What our tests found on the Philippine 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 Philippine proxies.
Almost every live entry here sits on a Philippine phone or internet provider. Only 2 of 113 carried our datacenter flag, against about one in five on ordinary addresses elsewhere.
At 02:12 UTC on September 28, 2026, our pool held 113 live Philippine entries among 477 in rotation. The checker had revisited 237 of those 477 within the previous thirty minutes.
A minute later our server in the United States tried all 112 rows then live. Eleven of them relayed a plain request, and each one exited inside the Philippines.
The 48-hour list agreed: 49 of its 461 rows relayed, and all 49 came out in the country.
Over a quarter of live entries were transparent, 31 of 113, so sites saw your own address. Where privacy or uptime matters, paid Philippine proxies are the better tool.
01
The Philippine slice against the rest
Below, 170 live Philippine entries at 13:36 UTC are compared with entries on ordinary addresses elsewhere.
| Measured September 28, 2026 | Philippines | Rest of the pool |
|---|---|---|
| Live entries measured | 170 | 4,079 |
| Median success rate across its own checks | 36.1% | 34.0% |
| Passed ten checks at 90 percent | 0% | 8.9% |
| Median latency from our server in the United States | 7,337 ms | 6,313 ms |
| Flagged as datacenter by our list | 1.2% | 22.2% |
Read at 13:36 UTC. Neither column counts an address with 20 or more live entries.
No live Philippine entry had passed ten checks at a 90 percent rate. Each took longer than half a second, and the median ran a little slower than the pool's.
02
PLDT, Globe and a long tail of small networks
PLDT, the Philippine Long Distance Telephone company, carried 64 of the 113 live entries at 02:12 UTC.
None of them carried the datacenter flag.
Globe Telecom held 22 more on two networks; APNIC's record names one of them GLOBE-MOBILE-5TH-GEN-AS.
Infinivan held 5, G Links 4, Converge and DITO 3 each, and twelve small networks one apiece.
Those twelve held the only two datacenter entries, one on Alibaba Cloud and one on a cable network.
Manila held 12 live entries, Cebu City 8, Quezon City and Pasig 7 each; 8 had no city.
03
About eleven days, with few early losses
By 13:36 UTC, 1,485 of 2,182 Philippine entries retired from ordinary addresses had never passed a check.
Elsewhere on ordinary addresses, 88.8 percent never answered, so Philippine entries fail less often.
In all, 885 Philippine entries worked and then stopped; each is timed from first sighting to last answer. We leave out 188 of them, which sat on five busy Alibaba Cloud addresses.
| Measured September 28, 2026 | Philippines | Rest of the pool |
|---|---|---|
| Worked, then stopped | 885 | 297,038 |
| Left out: on addresses with 20 or more | 188 | 261,481 |
| Left out: the evening of June 14 | 69 | 9,123 |
| Left out: other entries on Amazon's networks | 0 | 1,066 |
| Counted | 628 | 25,368 |
| Median lifespan of those counted | 11.0 days | 9.8 days |
| Of those counted, stopped within a day | 10.4% | 25.0% |
| Of those counted, lasted more than thirty days | 30.6% | 31.0% |
Read at 17:19 UTC, minus the June evening a checker fault marked some 128,000 entries dead.
A quarter of counted entries stopped within 3.5 days, where elsewhere a quarter lasted a day or less. Their median, 11 days, also beat the pool's 9.8.
04
What our relay test found
Each live entry got two requests from our server in the United States. The first asked ip-api.com to echo the exit address; the second opened Google over an encrypted link.
| Measured September 28, 2026 | Entries |
|---|---|
| Tested | 112 |
| Did not accept a connection | 82 |
| Relayed the plain web request | 11 |
| Of those, exiting in the Philippines | 11 |
| Of those, leaving from the listed address | 7 |
| Opened Google over an encrypted connection | 4 |
| Certificate did not verify | 0 |
Run from one server in the United States at 02:13 UTC; each exit's country came from ip-api.com.
At the median, a relay took about 8.8 seconds to answer; 19 other entries connected but relayed nothing.
Straight after, we tried all 461 rows of the 48-hour list from the same server. Of those, 49 relayed, every one exiting in the Philippines, and no certificate failed.
Both tests covered the same 112 live rows, run a few minutes apart on one server. Eleven relayed in the first, 19 in the second, and only 5 in both.
Thirty-seven minutes later, 9 of 132 live entries and 31 of 461 list rows relayed. Every exit was again in the Philippines, but only 8 of the 49 earlier list relays repeated.
05
Rows to skip, whichever list shows them
On September 28, two other free lists showed 32 Philippine rows on 154.83.2, a block Cloudflare's network carries.
Our checker had met all 32 in June, and not one passed a single check. None of the 164 addresses we saw in that block ever did.
The same lists showed 13 rows on five Alibaba Cloud addresses in Manila. All had worked once, and our engine retired the last of them on September 22.
06
Few blocks on Philippine networks
OONI, which measures internet censorship, ran 361,788 web tests from the Philippines in the month to September 28.
Only one matched a known block page, and 95.8 percent loaded normally. Facebook, YouTube and Reddit each loaded normally in over 99 percent of their tests.
So when a site fails through a Philippine row, suspect the row before the country.
07
Making a row work
Take the port with the address: no live address here answered on more than one port. Port 8082 served 33 of the 113 live entries, ahead of 8081 with 17 and 8080 with 13.
HTTP ran on 73 live entries and HTTPS on 59; SOCKS4 had 4, and SOCKS5 none.
Our proxy checker tests a row for status, speed and anonymity, and names its country and network.
Expect one success in ten tries at best: 11 of 112 live entries relayed, then 9 of 132.
Retry a row that fails, because relaying came and went within minutes in both runs.
Questions
Frequently asked.
Yes, if it relays at all: all 100 relays in our four tests exited in the Philippines. The tests ran on September 28, 2026, with every request sent from one American server of ours.
Slow: the median live entry needed 7,337 ms at 13:36 UTC, timed from our US checker. Other ordinary addresses in the pool took 6,313 ms, and our eleven relays a median 8.8 seconds.
Not for logins or payments: on September 28, 2026, 31 of 113 live entries were transparent. Those pass your address on, no free entry encrypts your traffic, and strangers share each one.
About eleven days: that was the median for entries that worked, against 9.8 in the wider pool. Few stop early: 10.4 percent went silent within a day, against 25.0 percent elsewhere. The count skips five Alibaba Cloud addresses with 20 or more such entries each, 188 in all. It also leaves out Amazon's networks and one faulty June evening.
HTTP leads with 73 of the 113 live entries, and port 8082 is the most common, at 33. No live entry offered SOCKS5 when we read the pool on September 28, 2026.
Sometimes: the list filed 12 live entries under Manila and 8 under Cebu City. Treat the city as an estimate, since 15 of 46 relays exited in another region than listed.
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.