Is 3.137.218.166:83 a proxy? Yes.
3.137.218.166:83 is a public HTTP proxy in the HProxy free proxy list. It holds a spotty 0% uptime, and was last checked just now.
How this one compares
1 attempts. Not one connection.
Being published on a proxy list is a claim that an address works. It is not a test, and nobody in that chain is obliged to have tried it. We tried 1 times, which is why the answer on this page is a flat no rather than a maybe.
0%
of 1 checks answered
Pool median 14.6%. 3.137.218.166:83 sits below it, which is ordinary for a public proxy.
1
real connection attempts
Each one opens a socket and waits up to 90 seconds. Slow and unreachable look identical if you stop listening early.
0
days in our records, never once answering
It is not in the lifespan figures at all: those cover the 196,722 endpoints that worked at least once before they stopped.
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 196,722 endpoints that stopped working.
Middle halfMedianFull range
How quickly one answers
Response time on the last successful check, across the 3,605 proxies answering right now.
How to use this proxy
Route a request through 3.137.218.166:83 over HTTP. Free proxies are shared and rotate out fast, so test before you rely on it.
curl -x http://3.137.218.166:83 \
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 3.137.218.166:83
3.137.218.166:83 is in the live pool right now, and it stays there only for as long as it keeps answering.
Port 83: System port
Ports below 1024 are protected. On most systems you need administrator rights to open one at all. So whatever is answering here was set up by someone with full control of that machine, not by some ordinary program that happened to be running.
Every failure here was measured, not assumed
Each check opens a real connection to 3.137.218.166:83 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. Nothing about this record is inherited from the list that published the address. 1 times HProxy tried, and 1 times the connection did not complete inside that budget, which is why the answer on this page is a flat no rather than a maybe. The handshake is attempted across HTTP, HTTPS, SOCKS4 and SOCKS5, which is how we know it spoke HTTP.
1 checks, zero connections
Not one of those 1 attempts reached a working proxy. The address stays in the database with that result attached, because "we tried 1 times and it never answered" is a far more useful answer than silence for anyone who found 3.137.218.166 somewhere and wants to know what it is.
It is being re-tested continuously
3.137.218.166:83 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 3.137.218.166:83, and nothing it does not.
- First seen
- August 23, 2026
- Last checked
- August 23, 2026
- Next check due
- continuously
- Checks run
- 1
- Times it answered
- 0
- Spoke
- HTTP
0%
never answered across 1 attempts
Questions about 3.137.218.166:83
Is 3.137.218.166:83 a working proxy right now?
Yes. 3.137.218.166:83 answered HProxy's automated check just now 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 3.137.218.166?
It speaks HTTP. The port is 83. Point your client at 3.137.218.166:83 over http to route a request through it.
How reliable has 3.137.218.166:83 been?
Across 1 day of tracking it answered 0% 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 3.137.218.166:83?
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.
Upgrade to the paid network
Free proxies fail. This is what that looks like.
3.137.218.166:83 answers 0% 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
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.