Is 84.201.144.65:10000 a proxy? Yes, it was.
84.201.144.65:10000 was a public proxy in the HProxy free proxy pool, exiting from RU on YandexCloud. Across 462 checks it answered 6% of the time, and it has since gone dark (last listed 2026-07-26), so it is not a usable proxy right now.
uptime while tracked
RussiaUptime & downtime
1
Days tracked
56
Checks run
100%
Downtime
1
Down days
Continuous monitoring
How HProxy checks 84.201.144.65:10000
HProxy has checked 84.201.144.65:10000 462 times and it answered 30 of those. Here is what each of those checks actually did.
16 public sources published it
84.201.144.65 appears in 16 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 10000: 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 84.201.144.65:10000 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.
462 checks, 30 answered
That is 6% of the time, measured since June 12, 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. 84.201.144.65:10000 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 84.201.144.65:10000, and nothing it does not.
- First seen
- June 12, 2026
- Last checked
- August 3, 2026
- Next check due
- within 24 hours
- Checks run
- 462
- Times it answered
- 30
- Stopped answering
- July 26, 2026
6%
answered 30 of 462 checks
Live free proxies right now
View all →
Where this address sits
Right now our free pool holds 2 other free proxies on Yandexcloud, and 118 in Russia. 84.201.144.65:10000 sits inside that set, so if it is not usable the pages below are where its closest alternatives are.
What HProxy holds on YandexCloud
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 134 addresses on AS200350, which is 0.02% of every address in the database and a small corner of the database. 5 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 now4%
- Answered before40%
- Never answered57%
Questions about 84.201.144.65:10000
Is 84.201.144.65:10000 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-26. We still re-test it periodically in case it returns.
Was 84.201.144.65 ever actually a proxy?
Yes. We ran 462 checks against it and it answered 30 of them, about 6% of the time, over 44 days on our list.
Where was 84.201.144.65 hosted?
Russia — YandexCloud (AS200350). 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 Yandexcloud?
2 other free proxies are live on Yandexcloud (AS200350) in our pool right now, alongside 84.201.144.65:10000. 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 Russia?
Yes, 118 free proxies are exiting from Russia in our pool right now, answering in 1242ms 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.