Is 54.235.192.64:442 a proxy? Yes.
54.235.192.64:442 is a public HTTP proxy in the HProxy free proxy list, exiting from United States. It holds a spotty 24% uptime with a high 1717ms response time, and last answered our checker 7 hr ago.
uptime
United StatesHow this one compares
283 checks in, its uptime is ordinary for a free proxy.
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 6,168 proxies answering right now, the middle of the pack answers 30.4% of the checks we send it.
24%
of 283 checks answered
Pool median 30.4%. 54.235.192.64:442 sits below it, which is ordinary for a public proxy.
1717ms
on its last response
Pool median 5,788ms, so this one is roughly 3x quicker than typical.
6
days tracked, still in the live pool
Of the 377,606 free proxies we have watched stop working, half were gone within 23 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 377,606 endpoints that stopped working.
Middle halfMedianFull range
How quickly one answers
Response time on the last successful check, across the 6,168 proxies answering right now.
Where this address sits
Right now our free pool holds no other free proxies on Amazon, and 21,762 in United States. 54.235.192.64:442 sits inside that set, so if it is not usable the pages below are where its closest alternatives are. At 1717ms it answers faster than the 2093ms median for United States proxies (about 82% of it).
Amazon.com, Inc. is the 27th 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 2,588 addresses on AS14618, which is 0.29% of every address in the database and a meaningful pocket of the database. That makes it the 27th largest source of free proxies of every network we have ever seen. 1 of them is answering right now, so if this particular address is not usable, the network is a reasonable place to look for one that is.
- Answering now<1%
- Answered before58%
- Never answered42%
- 1LimitedNetwork-ASAS213790227,474
- 2SECURED SERVERS LLCAS19437120,032
- 3M247AS900963,454
- 4SECURED SERVERS LLCAS2045456,868
- 5Amazon.com, Inc.AS1650948,795
- 6Cloudflare, Inc.AS1333522,930
- 7Cloudflare, Inc.AS20924214,278
- 8Alibaba (US) Technology Co., Ltd.AS4510212,355
18 networks between
27Amazon.com, Inc.AS146182,588
How to use this proxy
Route a request through 54.235.192.64:442 over HTTP. Free proxies are shared and rotate out fast, so test before you rely on it.
curl -x http://54.235.192.64:442 \
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 54.235.192.64:442
54.235.192.64:442 is in the live pool right now, and it stays there only for as long as it keeps answering.
Port 442: 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 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 54.235.192.64:442 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. 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 HTTP and HTTPS.
283 checks, 68 answered
That is 24% of the time, measured since September 30, 2026. Every one of those results, successes and failures alike, is a connection HProxy opened itself.
It is being re-tested continuously
54.235.192.64:442 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 54.235.192.64:442, and nothing it does not.
- First seen
- September 30, 2026
- Last checked
- October 6, 2026
- Next check due
- continuously
- Checks run
- 283
- Times it answered
- 68
- Spoke
- HTTP, HTTPS
24%
answered 68 of 283 checks
Questions about 54.235.192.64:442
Is 54.235.192.64:442 a working proxy right now?
Yes. 54.235.192.64:442 answered HProxy's automated check 7 hr 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 54.235.192.64?
It speaks HTTP, HTTPS, and our checks grade it transparent. The port is 442. Point your client at 54.235.192.64:442 over http to route a request through it.
Where is 54.235.192.64 located?
Traffic through it exits from Ashburn, United States, on Amazon.com, Inc. (AS14618). That is where the destination site will think your request came from.
How fast is 54.235.192.64:442?
It answered in 1717ms 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 54.235.192.64:442 been?
Across 7 days of tracking it answered 24% 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 54.235.192.64:442?
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 Amazon?
None other than 54.235.192.64:442 at the moment. AS14618 (Amazon) has no other free proxies live in our pool right now, though that changes as we re-verify.
Are there other free proxies in United States?
Yes, 21,762 free proxies are exiting from United States in our pool right now, answering in 2093ms 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.
54.235.192.64:442 answers 24% 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 all3.235.0.113:2024
HTTPS · United States · 6% · 115ms
184.72.79.151:22265
HTTPS · United States · 14% · 163ms
3.211.120.181:443
HTTP · United States · 49% · 550ms
184.72.77.68:1001
HTTP · United States · 7% · 1043ms
3.90.45.120:3128
HTTP · United States · 100% · 9591ms
198.199.86.11:8080
HTTP · United States · 89% · 63ms
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.