Is 45.144.54.40:1081 a proxy? It was listed.
45.144.54.40:1081 was listed as a public proxy in 15 of our sources. Since August 9, 2026 we have tried it 4 times and it has never answered us. It may have worked before we started watching. We keep re-testing it around the clock in case it comes back.
GermanyUptime & downtime
1
Days tracked
2
Checks run
100%
Downtime
1
Down days
How this one compares
4 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 4 times, which is why the answer on this page is a flat no rather than a maybe.
0%
of 4 checks answered
Pool median 15.6%. 45.144.54.40:1081 sits below it, which is ordinary for a public proxy.
4
real connection attempts
Each one opens a socket and waits up to 90 seconds. Slow and dead 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 192,453 endpoints that worked at least once before they stopped.
August 9, 2026
First listed by our sources
Published as a working proxy by 15 of the public lists HProxy tracks. Being listed is a claim, not a test.
August 10, 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.
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,453 endpoints that stopped working.
Middle halfMedianFull range
How quickly one answers
Response time on the last successful check, across the 3,797 proxies answering right now.
Continuous monitoring
How HProxy checks 45.144.54.40:1081
HProxy has opened a connection to 45.144.54.40:1081 4 times and it has never once answered. That is a measurement, not an assumption, and it is the difference between this record and the lists that republished the address without testing it.
15 public sources published it
45.144.54.40 appears in 15 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.
Port 1081: SOCKS, alternate
Port 1081 is where the second SOCKS tunnel goes when 1080 on the same machine is already busy. Seeing it usually means somebody set up more than one.
Every failure here was measured, not assumed
Each check opens a real connection to 45.144.54.40:1081 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. Nothing about this record is inherited from the list that published the address. 4 times HProxy tried, and 4 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, so a proxy is never missed because we guessed the wrong protocol.
4 checks, zero connections
Not one of those 4 attempts reached a working proxy. The address stays in the database with that result attached, because "we tried 4 times and it never answered" is a far more useful answer than silence for anyone who found 45.144.54.40 somewhere and wants to know what it is.
It is still re-tested every 24 hours
45.144.54.40:1081 has never answered, and it is still in the rotation anyway. The sweep reaches every address in the database roughly once every 24 hours regardless of its history, because an address that was dark for months can be brought back online by whoever controls it without telling anybody. Its last check was on August 10, 2026, so the next one is due within a day of that. If that ever happens here, this page changes on its own.
This endpoint
The record
Everything HProxy holds on 45.144.54.40:1081, and nothing it does not.
- First seen
- August 9, 2026
- Last checked
- August 10, 2026
- Next check due
- within 24 hours
- Checks run
- 4
- Times it answered
- 0
- Stopped answering
- August 9, 2026
0%
never answered across 4 attempts
Live free proxies right now
View all →
Where this address sits
Right now our free pool holds 10 other free proxies on AEZA AS, and 313 in Germany. 45.144.54.40:1081 sits inside that set, so if it is not usable the pages below are where its closest alternatives are.
AEZA-AS is the 60th 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 903 addresses on AS210644, which is 0.15% of every address in the database and a meaningful pocket of the database. That makes it the 60th largest source of free proxies of every network we have ever seen. 10 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 before24%
- Never answered75%
- 1LimitedNetwork-ASAS213790227,266
- 2Amazon.com, Inc.AS1650925,791
- 3Cloudflare, Inc.AS1333522,185
- 4SECURED SERVERS LLCAS2045419,475
- 5Cloudflare, Inc.AS20924214,136
- 6Alibaba (US) Technology Co., Ltd.AS4510211,648
- 7GloboTech CommunicationsAS3666611,542
- 8ChinanetAS41348,355
51 networks between
60AEZA-ASAS210644903
Questions about 45.144.54.40:1081
Is 45.144.54.40:1081 a working proxy?
Not for us. 45.144.54.40:1081 was published as a public proxy by our sources, and across 4 checks since August 9, 2026 it has never answered.
Was 45.144.54.40 ever actually a proxy?
Not while we have been watching it, which is the honest limit of what we can say. Our record opens on August 9, 2026, and across 4 checks since then it has never answered us. 15 separate lists published it as a working proxy, so it may well have answered somebody before we first tested it. We report what we measured, not what we assume.
Where was 45.144.54.40 hosted?
Frankfurt am Main, Hesse, Germany, AEZA-AS (AS210644). 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 AEZA AS?
10 other free proxies are live on AEZA AS (AS210644) in our pool right now, alongside 45.144.54.40:1081. 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 Germany?
Yes, 313 free proxies are exiting from Germany in our pool right now, answering in 2037ms 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.
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.