Is 212.34.138.89:8080 a proxy? Yes.
212.34.138.89:8080 is a public HTTPS proxy in the HProxy free proxy list, exiting from Netherlands. It holds a spotty 15% uptime with a high 4685ms response time, and was last checked 16 min ago.
uptime
Uptime & downtime
7
Days tracked
355
Checks run
88.2%
Downtime
7
Down days
How this one compares
Ordinary on uptime, and here is what ordinary means.
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 3,846 proxies answering right now, the middle of the pack answers 15.2% of the checks we send it.
15%
of 1,003 checks answered
Pool median 15.2%. 212.34.138.89:8080 sits below it, which is ordinary for a public proxy.
4685ms
on its last response
Pool median 1,915ms.
18
days tracked, still in the live pool
Of the 192,619 free proxies we have watched stop working, half were gone within 28 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 192,619 endpoints that stopped working.
Middle halfMedianFull range
How quickly one answers
Response time on the last successful check, across the 3,846 proxies answering right now.
Where this address sits
Right now our free pool holds 5 other free proxies on Vdsina, and 50 in Netherlands. 212.34.138.89:8080 sits inside that set, so if it is not usable the pages below are where its closest alternatives are. At 4685ms it answers faster than the 7393ms median for Netherlands proxies (about 63% of it).
VDSINA is the 119th largest source of free proxies we have ever measured.
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 353 addresses on AS216071, which is 0.06% of every address in the database and a small corner of the database. That makes it the 119th largest source of free proxies of every network we have ever seen. 6 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 now2%
- Answered before32%
- Never answered66%
- 1LimitedNetwork-ASAS213790227,266
- 2Amazon.com, Inc.AS1650926,197
- 3Cloudflare, Inc.AS1333522,185
- 4SECURED SERVERS LLCAS2045419,475
- 5Cloudflare, Inc.AS20924214,136
- 6Alibaba (US) Technology Co., Ltd.AS4510211,650
- 7GloboTech CommunicationsAS3666611,542
- 8ChinanetAS41348,361
110 networks between
119VDSINAAS216071353
How to use this proxy
Route a request through 212.34.138.89:8080 over HTTPS. Free proxies are shared and rotate out fast, so test before you rely on it.
curl -x https://212.34.138.89:8080 \
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 212.34.138.89:8080
212.34.138.89:8080 is in the live pool right now, and it stays there only for as long as it keeps answering.
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 212.34.138.89:8080 and gives it up to 90 seconds to answer. Slow is not the same as dead, 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 HTTPS.
1,003 checks, 155 answered
That is 15% of the time, measured since July 24, 2026. Every one of those results, successes and failures alike, is a connection HProxy opened itself.
It is being re-tested continuously
212.34.138.89:8080 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 212.34.138.89:8080, and nothing it does not.
- First seen
- July 24, 2026
- Last checked
- August 11, 2026
- Next check due
- continuously
- Checks run
- 1,003
- Times it answered
- 155
- Spoke
- HTTPS
15%
answered 155 of 1,003 checks
Questions about 212.34.138.89:8080
Is 212.34.138.89:8080 a working proxy right now?
Yes. 212.34.138.89:8080 answered HProxy's automated check 16 min 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 212.34.138.89?
It speaks HTTPS, and our checks grade it elite. The port is 8080. Point your client at 212.34.138.89:8080 over https to route a request through it.
Where is 212.34.138.89 located?
Traffic through it exits from Amsterdam, Netherlands, on VDSINA (AS216071). That is where the destination site will think your request came from.
How fast is 212.34.138.89:8080?
It answered in 4685ms 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 212.34.138.89:8080 been?
Across 19 days of tracking it answered 15% 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 212.34.138.89:8080?
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 Vdsina?
5 other free proxies are live on Vdsina (AS216071) in our pool right now, alongside 212.34.138.89:8080. 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, 50 free proxies are exiting from Netherlands in our pool right now, answering in 7393ms 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.
212.34.138.89:8080 answers 15% 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 all →88.210.11.216:8989
HTTP · Netherlands · 43% · 2842ms
144.124.227.88:3128
HTTP · Netherlands · 59% · 3840ms
5.35.71.232:10808
HTTP · Netherlands · 50% · 6494ms
89.110.124.45:8888
HTTP · Netherlands · 42% · 18695ms
80.85.247.71:1234
HTTP · Netherlands · 4% · 0ms
204.76.203.9:3128
HTTP · Netherlands · 100% · 287ms
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.