Is 89.208.106.37:32712 a proxy? Yes.
89.208.106.37:32712 is a public SOCKS5 proxy in the HProxy free proxy list, exiting from Netherlands. It holds a solid 84% uptime with a high 3232ms response time, and was last checked 17 min ago.
uptime
NetherlandsUptime & downtime
2
Days tracked
62
Checks run
16.1%
Downtime
1
Down days
How this one compares
Reliable enough to sit in the top 5% of everything we are watching.
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 8,324 proxies answering right now, the middle of the pack answers 14% of the checks we send it.
84%
of 62 checks answered
Pool median 14%. 89.208.106.37:32712 is in the top 5%.
3232ms
on its last response
Pool median 1,772ms.
1
days tracked, still in the live pool
Of the 193,245 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 193,245 endpoints that stopped working.
Middle halfMedianFull range
How quickly one answers
Response time on the last successful check, across the 8,324 proxies answering right now.
Where this address sits
Right now our free pool holds 6 other free proxies on AEZA AS, and 66 in Netherlands. 89.208.106.37:32712 sits inside that set, so if it is not usable the pages below are where its closest alternatives are. At 3232ms it answers faster than the 4642ms median for Netherlands proxies (about 70% of it).
AEZA-AS is the 59th 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 915 addresses on AS210644, which is 0.15% of every address in the database and a meaningful pocket of the database. That makes it the 59th largest source of free proxies of every network we have ever seen. 7 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 now1%
- Answered before25%
- Never answered75%
- 1LimitedNetwork-ASAS213790227,266
- 2Amazon.com, Inc.AS1650926,795
- 3Cloudflare, Inc.AS1333522,185
- 4SECURED SERVERS LLCAS2045419,475
- 5Cloudflare, Inc.AS20924214,139
- 6Alibaba (US) Technology Co., Ltd.AS4510211,674
- 7GloboTech CommunicationsAS3666611,542
- 8ChinanetAS41348,372
50 networks between
59AEZA-ASAS210644915
How to use this proxy
Route a request through 89.208.106.37:32712 over SOCKS5. Free proxies are shared and rotate out fast, so test before you rely on it.
curl -x socks5://89.208.106.37:32712 \
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 89.208.106.37:32712
89.208.106.37:32712 is in the live pool right now, and it stays there only for as long as it keeps answering.
Port 32712: Registered port range
This port sits in the middle range, where any ordinary program can listen without special permission. The number itself carries no reserved meaning, which tells you somebody picked it on purpose instead of accepting a 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 a real connection to 89.208.106.37:32712 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 SOCKS5.
62 checks, 52 answered
That is 84% of the time, measured since August 12, 2026. Every one of those results, successes and failures alike, is a connection HProxy opened itself.
It is being re-tested continuously
89.208.106.37:32712 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 89.208.106.37:32712, and nothing it does not.
- First seen
- August 12, 2026
- Last checked
- August 13, 2026
- Next check due
- continuously
- Checks run
- 62
- Times it answered
- 52
- Spoke
- SOCKS5
84%
answered 52 of 62 checks
Questions about 89.208.106.37:32712
Is 89.208.106.37:32712 a working proxy right now?
Yes. 89.208.106.37:32712 answered HProxy's automated check 17 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 89.208.106.37?
It speaks SOCKS5, and our checks grade it elite. The port is 32712. Point your client at 89.208.106.37:32712 over socks5 to route a request through it.
Where is 89.208.106.37 located?
Traffic through it exits from Amsterdam, Netherlands, on AEZA-AS (AS210644). That is where the destination site will think your request came from.
How fast is 89.208.106.37:32712?
It answered in 3232ms 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 89.208.106.37:32712 been?
Across 2 days of tracking it answered 84% 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 89.208.106.37:32712?
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 AEZA AS?
6 other free proxies are live on AEZA AS (AS210644) in our pool right now, alongside 89.208.106.37:32712. 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, 66 free proxies are exiting from Netherlands in our pool right now, answering in 4642ms 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.
89.208.106.37:32712 answers 84% 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 →
79.137.184.208:1080
SOCKS4 · Finland · 100% · 876ms
147.45.72.212:44816
SOCKS4 · Sweden · 17% · 5580ms
45.137.43.0:1081
SOCKS4 · Germany · 72% · 7501ms
62.60.238.191:443
HTTP · Austria · 41% · 10264ms
77.221.149.55:3128
HTTP · United States · 43% · 10511ms
46.226.162.25:3128
HTTP · United Kingdom · 24% · 15028ms
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.