Is 178.227.164.157:8080 a proxy? Yes, it was.
178.227.164.157:8080 was a public proxy in the HProxy free proxy pool, exiting from Netherlands on Odido. Across 193 checks it answered 8% of the time, and it has since gone dark (last answered October 5, 2026), so it is not a usable proxy right now.
across all 193 checks
NetherlandsHow this one compares
It worked sometimes, for 0 days, and then it stopped.
Every free proxy list quotes an uptime figure. Almost none of them tell you what a normal one looks like, so here is ours: across the 7,568 proxies answering right now, the middle of the pack answers 35% of the checks we send it.
8%
of 193 checks answered
Pool median 35%. 178.227.164.157:8080 sits below it, which is ordinary for a public proxy.
193
real connection attempts
Each one opens a socket and waits up to 90 seconds. Slow and unreachable look identical if you stop listening early.
0
days from first sighting to last answer
Of the 393,476 free proxies we have watched stop working, half were gone within 22 days of us first seeing them.
October 5, 2026
First listed by our sources
Published as a working proxy by 21 of the public lists HProxy tracks. Being listed is a claim, not a test.
October 8, 2026
Moved to the permanent record
It left the live pool here. Nothing is deleted: the address keeps this page and stays in the re-check rotation.
October 12, 2026
Most recent re-test
HProxy has opened 193 real connections to this endpoint in total. The sweep reaches every address in the database roughly once every 12 hours.
What normal looks like
Every number above is measured against these two.
A percentage on a proxy list means nothing without the shape of the thing it came from. These are the two distributions the rest of this page compares against, drawn from HProxy's own checks rather than from anybody's marketing page.
How long one lasts
Days from the first time we saw an address to the last time it answered, across 393,476 endpoints that stopped working.
Middle halfMedianFull range
How quickly one answers
Response time on the last successful check, across the 7,568 proxies answering right now.
Continuous monitoring
How HProxy checks 178.227.164.157:8080
HProxy has checked 178.227.164.157:8080 193 times and it answered 15 of those. Every one of those was a real connection attempt, never a lookup.
21 public sources published it
178.227.164.157 appears in 21 of the public proxy sources HProxy tracks. Lists copy from each other constantly, so an address showing up in many of them says a lot about how widely it was republished and very little about whether it ever worked.
Port 8080: HTTP, alternate
Port 8080 is the most common proxy port on the internet. It stands in for port 80, and unlike port 80 any program can open it without administrator rights. That single detail is why so much ends up here, the deliberate and the accidental alike.
Every check is a real connection
HProxy does not read this address off somebody else's list and pass it on. Each check opens a real connection to 178.227.164.157:8080 and gives it up to 90 seconds to answer. Slow is not the same as unreachable, and plenty of working proxies take half a minute to reply. Anything that does not answer in that budget counts as a failure and is recorded as one, which is why the percentage on this page moves rather than sitting at a marketing number. The handshake is attempted across HTTP, HTTPS, SOCKS4 and SOCKS5, so a proxy is never missed because we guessed the wrong protocol.
193 checks, 15 answered
That is 8% of the time, measured since October 5, 2026. Every one of those results, successes and failures alike, is a connection HProxy opened itself.
We are still watching for it to come back
Being archived does not stop the testing. 178.227.164.157:8080 answered before, so it is exactly the kind of address that can return, and the sweep works through the whole database and reaches every address roughly once every 12 hours. Its last check was on October 12, 2026, so the next one is due within a day of that. The moment it answers again it is promoted straight back into the live free proxy list, automatically, with no manual step.
This endpoint
The record
Everything HProxy holds on 178.227.164.157:8080, and nothing it does not.
- First seen
- October 5, 2026
- Last checked
- October 12, 2026
- Next check due
- within 12 hours
- Checks run
- 193
- Times it answered
- 15
- Stopped answering
- October 5, 2026
8%
answered 15 of 193 checks
Live free proxies right now
View allWhere this address sits
Right now our free pool holds no other free proxies on Odido, and 249 in Netherlands. 178.227.164.157:8080 sits inside that set, so if it is not usable the pages below are where its closest alternatives are.
How many free proxies are on Odido
Open proxies cluster rather than spreading evenly across the internet. Hosting providers and cloud platforms run enormous numbers of near-identical servers, so a handful of networks end up carrying a disproportionate share of every public proxy list, including ours. HProxy tracks 10 addresses on AS31615, which is 0.00% of every address in the database and a small corner of the database. None of them are answering at the moment, though every one stays in the re-check rotation in case that changes.
- Answered before70%
- Never answered30%
- 1LimitedNetwork-ASAS213790227,474
- 2SECURED SERVERS LLCAS19437120,032
- 3M247AS900977,268
- 4SECURED SERVERS LLCAS2045456,868
- 5Amazon.com, Inc.AS1650949,796
- 6Cloudflare, Inc.AS1333522,931
- 7Cloudflare, Inc.AS20924214,280
- 8Alibaba (US) Technology Co., Ltd.AS4510212,381
- AS31615 sits outside the 250 largest networks we hold.
Questions about 178.227.164.157:8080
Is 178.227.164.157:8080 a working proxy?
No, not any more. It was a working public proxy in HProxy's free pool and has since gone dark, last answering on October 5, 2026. We still re-test it periodically in case it returns.
Was 178.227.164.157 ever actually a proxy?
Yes. We ran 193 checks against it and it answered 15 of them, about 8% of the time, over under a day on our list.
What is the hostname for 178.227.164.157?
178.227.164.157 publishes no reverse DNS record. That is not unusual and it is not suspicious on its own, but it does mean the address volunteers nothing about who runs it, so the network and the check history below are all there is to go on.
Where was 178.227.164.157 hosted?
Utrecht, Utrecht, Netherlands, Odido (AS31615). It is a residential or ISP address rather than a datacenter one.
Why keep a page for an address that no longer works?
Because "was this address ever a proxy, and when" is a real question. If you are looking at this IP in a firewall log or an abuse report, the dates and the check counts here are the answer. HProxy's public proxy IP list keeps every address it has ever tracked and carries on re-testing them, so deleting this record would throw all of that away.
How many free proxies are on Odido?
None other than 178.227.164.157:8080 at the moment. AS31615 (Odido) has no other free proxies live in our pool right now, though that changes as we re-verify.
Are there other free proxies in Netherlands?
Yes, 249 free proxies are exiting from Netherlands in our pool right now, answering in 716ms at the median. If this address is not usable, that list is the place to look for a working one.
Where to go next
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.
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.