Is 80.73.89.126:65056 a proxy? Yes.
80.73.89.126:65056 is a public HTTP proxy in the HProxy free proxy list, exiting from Russia. It holds a spotty 4% uptime with a high 2634ms response time, and last answered our checker 6 hr ago.
RussiaHow this one compares
552 checks in, its uptime is ordinary for a free proxy.
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,676 proxies answering right now, the middle of the pack answers 30.9% of the checks we send it.
4%
of 552 checks answered
Pool median 30.9%. 80.73.89.126:65056 sits below it, which is ordinary for a public proxy.
2634ms
on its last response
Pool median 5,738ms, so this one is roughly 2x quicker than typical.
129
days tracked, still in the live pool
Of the 403,496 free proxies we have watched stop working, half were gone within 21 days of us first seeing them.
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 403,496 endpoints that stopped working.
Middle halfMedianFull range
How quickly one answers
Response time on the last successful check, across the 7,676 proxies answering right now.
Where this address sits
Right now our free pool holds no other free proxies on PJSC "Rostelecom". Yakutsk branch, and 510 in Russia. 80.73.89.126:65056 sits inside that set, so if it is not usable the pages below are where its closest alternatives are. At 2634ms it answers faster than the 3573ms median for Russia proxies (about 74% of it).
How many free proxies are on PJSC "Rostelecom". Yakutsk branch
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 6 addresses on AS21487, 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 before33%
- Never answered67%
- 1LimitedNetwork-ASAS213790227,474
- 2SECURED SERVERS LLCAS19437120,032
- 3M247AS900992,270
- 4SECURED SERVERS LLCAS2045456,868
- 5Amazon.com, Inc.AS1650950,695
- 6Cloudflare, Inc.AS1333522,934
- 7Cloudflare, Inc.AS20924214,281
- 8Alibaba (US) Technology Co., Ltd.AS4510212,420
- AS21487 sits outside the 250 largest networks we hold.
How to use this proxy
Route a request through 80.73.89.126:65056 over HTTP. Free proxies are shared and rotate out fast, so test before you rely on it.
curl -x http://80.73.89.126:65056 \
https://api.ipify.org?format=json
Not a terminal person? Pick your device and we walk you through it, nothing assumed.
Continuous monitoring
How HProxy checks 80.73.89.126:65056
80.73.89.126:65056 is in the live pool right now, and it stays there only for as long as it keeps answering.
Port 65056: Ephemeral port range
This is a throwaway port number, the kind a computer hands out for a few minutes and then takes back. Anything published on one tends to move or disappear when its host restarts, which is a large part of why public proxy lists rot so fast.
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 80.73.89.126:65056 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, which is how we know it spoke HTTP.
552 checks, 22 answered
That is 4% of the time, measured since June 11, 2026. Every one of those results, successes and failures alike, is a connection HProxy opened itself.
It is being re-tested continuously
80.73.89.126:65056 is in the live rotation, so it is re-tested continuously rather than on a daily cycle. If it stops answering it is marked down immediately, and if it stays down for 3 days it moves into the public proxy database with its full record intact. Nothing is deleted at any point.
This endpoint
The record
Everything HProxy holds on 80.73.89.126:65056, and nothing it does not.
- First seen
- June 11, 2026
- Last checked
- October 18, 2026
- Next check due
- continuously
- Checks run
- 552
- Times it answered
- 22
- Spoke
- HTTP
4%
answered 22 of 552 checks
Questions about 80.73.89.126:65056
Is 80.73.89.126:65056 a working proxy right now?
Yes. 80.73.89.126:65056 answered HProxy's automated check 6 hr ago and is in the live free proxy pool as we publish this page. It is re-tested every few minutes, so open this page again for its current state rather than trusting a copy of it.
What kind of proxy is 80.73.89.126?
It speaks HTTP, and our checks grade it anonymous. The port is 65056. Point your client at 80.73.89.126:65056 over http to route a request through it.
Where is 80.73.89.126 located?
Traffic through it exits from Russia, on PJSC "Rostelecom". Yakutsk branch (AS21487). That is where the destination site will think your request came from.
How fast is 80.73.89.126:65056?
It answered in 2634ms on the last check. Free public proxies are shared, so real-world speed varies with how many other people are using it at the same moment.
How reliable has 80.73.89.126:65056 been?
Across 57 days of tracking it answered 4% of our checks. The chart on this page shows every day we have recorded for it, including the days it was down.
Is it safe to use 80.73.89.126:65056?
Treat it the way you would any public proxy: it is operated by someone we have no relationship with, it is shared with strangers, and anything you send unencrypted over it can be read. Fine for a quick geo check or a scrape of public data, never for logins, payments or anything private.
How many free proxies are on PJSC "Rostelecom". Yakutsk branch?
None other than 80.73.89.126:65056 at the moment. AS21487 (PJSC "Rostelecom". Yakutsk branch) has no other free proxies live in our pool right now, though that changes as we re-verify.
Are there other free proxies in Russia?
Yes, 510 free proxies are exiting from Russia in our pool right now, answering in 3573ms 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
Free proxies fail. This is what that looks like.
80.73.89.126:65056 answers 4% of the time, and that is ordinary for a public proxy. Nothing here is a service anybody sells you, which is why the numbers swing and why the list turns over constantly.
Other live free proxies
View allAbout 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.