Is 83.238.125.220:8000 a proxy? Yes, it was.

83.238.125.220:8000 was a public proxy in the HProxy free proxy pool, exiting from Poland on Warszawa 02-822. Across 51 checks it answered 6% of the time, and it has since gone dark (last answered June 14, 2026), so it is not a usable proxy right now.

Not responding
6%

across all 51 checks

Checks run51
Times online3
First listedMay 22, 2026
Last checkedAugust 13, 2026
Listed for23 days
HostingResidential / ISP
CountryPL Poland

How this one compares

It worked sometimes, for 23 days, and then it stopped.

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 10,301 proxies answering right now, the middle of the pack answers 13.8% of the checks we send it.

6%

of 51 checks answered

median 13.8%

Pool median 13.8%. 83.238.125.220:8000 sits below it, which is ordinary for a public proxy.

51

real connection attempts

Each one opens a socket and waits up to 90 seconds. Slow and dead look identical if you stop listening early.

23

days from first sighting to last answer

Of the 193,304 free proxies we have watched stop working, half were gone within 28 days of us first seeing them.

The record on 83.238.125.220:8000Every date HProxy holds for this one endpoint, in order.
  1. May 22, 2026

    First listed by our sources

    Published as a working proxy by 5 of the public lists HProxy tracks. Being listed is a claim, not a test.

  2. June 14, 2026

    Stopped answering

    It answered our checks for 23 days before it went quiet.

  3. June 17, 2026

    Moved to the permanent record

    It left the live pool here. Nothing is deleted: the address keeps this page and stays in the re-check rotation.

  4. August 13, 2026

    Most recent re-test

    HProxy has opened 51 real connections to this endpoint in total. The sweep reaches every address in the database roughly once every 24 hours.

83.238.125.220:8000 answered for 23 days and has been re-tested 51 times in total. It is still in the rotation in case it comes back.
Source: HProxy verification engine · hproxy.comProxy.

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.

What a normal free proxy looks likeTwo distributions from HProxy's own checks rather than from anybody's marketing page. Tails trimmed at the 5th and 95th percentile.

How long one lasts

Days from the first time we saw an address to the last time it answered, across 193,304 endpoints that stopped working.

Proxies that diedmedian 28 days
0204060

Middle halfMedianFull range

Half of the free proxies we have watched stop working were gone within 28 days of us first seeing them.

How quickly one answers

Response time on the last successful check, across the 10,301 proxies answering right now.

Live free proxiesmedian 1,639ms
02,5005,0007,50010k
The spread runs from 128ms to 9,029ms across the same list.
Source: HProxy verification engine · hproxy.comProxy.

Continuous monitoring

How HProxy checks 83.238.125.220:8000

HProxy has checked 83.238.125.220:8000 51 times and it answered 3 of those. Every one of those was a real connection attempt, never a lookup.

  1. 5 public sources published it

    83.238.125.220 appears in 5 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.

  2. Port 8000: HTTP, alternate

    Port 8000 is one of the standard stand-ins for port 80. Development servers and device admin tools default to it constantly, so it is one of the busiest alternate web ports there is.

  3. 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 83.238.125.220:8000 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, so a proxy is never missed because we guessed the wrong protocol.

  4. 51 checks, 3 answered

    That is 6% of the time, measured since May 22, 2026. Every one of those results, successes and failures alike, is a connection HProxy opened itself.

  5. We are still watching for it to come back

    Being archived does not stop the testing. 83.238.125.220:8000 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 13, 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 83.238.125.220:8000, and nothing it does not.

First seen
May 22, 2026
Last checked
August 13, 2026
Next check due
within 24 hours
Checks run
51
Times it answered
3
Stopped answering
June 14, 2026

6%

answered 3 of 51 checks

Where this address sits

Right now our free pool holds no other free proxies on Warszawa 02-822, and 15 in Poland. 83.238.125.220:8000 sits inside that set, so if it is not usable the pages below are where its closest alternatives are.

How many free proxies are on Warszawa 02-822

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 78 addresses on AS12741, which is 0.01% 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.

AS12741 in the public proxy database
  • Answered before8%
  • Never answered92%
Most addresses published on this network never worked. That is the normal shape of a scraped proxy list, and it is only visible because every one of them was actually tested.Source: HProxy verification engine
The networks that host the most free proxiesAddresses in HProxy's public proxy list, by network. AS12741 is marked.
  1. 1LimitedNetwork-ASAS213790227,266
  2. 2Amazon.com, Inc.AS1650926,917
  3. 3Cloudflare, Inc.AS1333522,185
  4. 4SECURED SERVERS LLCAS2045419,475
  5. 5Cloudflare, Inc.AS20924214,140
  6. 6Alibaba (US) Technology Co., Ltd.AS4510211,676
  7. 7GloboTech CommunicationsAS3666611,542
  8. 8ChinanetAS41348,372
  9. AS12741 sits outside the 250 largest networks we hold.
Source: HProxy verification engine · hproxy.comProxy.
Is 83.238.125.220:8000 a proxy? It was: a free proxy in Poland that answered 6% of 51 checks before going dark, recorded by HProxy.
83.238.125.220:8000 at a glance. Its record stays published even though the address is no longer usable.

Questions about 83.238.125.220:8000

Is 83.238.125.220:8000 a working proxy?

No, not any more. It was a working public proxy in HProxy's free pool and has since gone dark, last answering on June 14, 2026. We still re-test it periodically in case it returns.

Was 83.238.125.220 ever actually a proxy?

Yes. We ran 51 checks against it and it answered 3 of them, about 6% of the time, over 23 days on our list.

What is the hostname for 83.238.125.220?

Its reverse DNS record is 83-238-125-220.static.ip.netia.com.pl. That is what the address itself publishes about who operates it, which is often more telling than the network name: hosting providers name their machines by region and instance type, and a residential line usually carries its ISP's own pattern.

Where was 83.238.125.220 hosted?

Kielce, Swietokrzyskie, Poland, Warszawa 02-822 (AS12741). 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 Warszawa 02-822?

None other than 83.238.125.220:8000 at the moment. AS12741 (Warszawa 02-822) has no other free proxies live in our pool right now, though that changes as we re-verify.

Are there other free proxies in Poland?

Yes, 15 free proxies are exiting from Poland in our pool right now, answering in 475ms 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.

Clean residential poolsCity-level targetingSticky sessions up to 24 h

Starting from

$0.44/GB

Billed per GB · balance never expires

Get started freeCompare plans & pricing
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.