Is 117.55.203.158:8899 a proxy? Yes, it was.
117.55.203.158:8899 was a public proxy in the HProxy free proxy pool, exiting from NL on PUSHPKT. Across 806 checks it answered 43% of the time, and it has since gone dark (last listed 2026-07-16), so it is not a usable proxy right now.
uptime while tracked
Uptime & downtime
0
Days tracked
0
Checks run
—
Downtime
0
Down days
Continuous monitoring
How HProxy checks 117.55.203.158:8899
HProxy has checked 117.55.203.158:8899 806 times and it answered 348 of those. Here is what each of those checks actually did.
46 public sources published it
117.55.203.158 appears in 46 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 8899: Registered port range
This port sits in the registered range, which any user-level program may listen on without special rights. It carries no reserved meaning of its own, so the number tells you the proxy was configured deliberately on a chosen port rather than on a system default.
Every check is a real connection
HProxy does not read this address off somebody else's list and pass it on. Each check opens an actual connection to 117.55.203.158:8899 and waits up to 4 seconds for the other end to complete a proxy handshake. 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.
806 checks, 348 answered
That is 43% of the time, measured since June 10, 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. 117.55.203.158:8899 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 24 hours. Its last check was on August 3, 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 117.55.203.158:8899, and nothing it does not.
- First seen
- June 10, 2026
- Last checked
- August 3, 2026
- Next check due
- within 24 hours
- Checks run
- 806
- Times it answered
- 348
- Stopped answering
- July 16, 2026
43%
answered 348 of 806 checks
Live free proxies right now
View all →Where this address sits
Right now our free pool holds 1 other free proxy on Pushpkt, and 62 in Netherlands. 117.55.203.158:8899 sits inside that set, so if it is not usable the pages below are where its closest alternatives are.
What HProxy holds on PUSHPKT
Open proxies are not spread evenly across the internet. They cluster, because one misconfigured template, one cheap hosting reseller or one leaked image tends to produce hundreds of identical machines on the same network. HProxy tracks 20 addresses on AS3920, which is 0.00% of every address in the database and a small corner of the database. 3 of them are answering right now, so if this particular address is not usable, the network is a reasonable place to look for one that is.
- Answering now15%
- Answered before45%
- Never answered40%
Questions about 117.55.203.158:8899
Is 117.55.203.158:8899 a working proxy?
No, not any more. It was a working public proxy in HProxy's free pool and has since gone dark, last listed 2026-07-16. We still re-test it periodically in case it returns.
Was 117.55.203.158 ever actually a proxy?
Yes. We ran 806 checks against it and it answered 348 of them, about 43% of the time, over 36 days on our list.
Where was 117.55.203.158 hosted?
Netherlands — PUSHPKT (AS3920). It is a datacenter address, not a home connection.
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 Pushpkt?
1 other free proxy is live on Pushpkt (AS3920) in our pool right now, alongside 117.55.203.158:8899. Networks that host one open proxy usually host several, which is why the whole AS is worth browsing rather than just this address.
Are there other free proxies in Netherlands?
Yes, 62 free proxies are exiting from Netherlands in our pool right now, answering in 239ms at the median. If this address is not usable, that list is the place to look for a working one.
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.