Is 134.35.10.155:8080 a proxy? Yes, it was.
134.35.10.155:8080 was a public proxy in the HProxy free proxy pool, exiting from Yemen on PTC-YemenNet. Across 224 checks it answered 0% of the time, and it has since gone dark (last answered July 22, 2026), so it is not a usable proxy right now.
across all 224 checks
YemenHow this one compares
224 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 224 times, which is why the answer on this page is a flat no rather than a maybe.
0%
of 224 checks answered
Pool median 38.2%. 134.35.10.155:8080 sits below it, which is ordinary for a public proxy.
224
real connection attempts
Each one opens a socket and waits up to 90 seconds. Slow and unreachable look identical if you stop listening early.
45
days in our records, never once answering
It is not in the lifespan figures at all: those cover the 200,835 endpoints that worked at least once before they stopped.
June 7, 2026
First listed by our sources
Published as a working proxy by 9 of the public lists HProxy tracks. Being listed is a claim, not a test.
July 22, 2026
Stopped answering
It answered our checks for 45 days before it went quiet.
July 25, 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.
August 31, 2026
Most recent re-test
HProxy has opened 224 real connections to this endpoint in total. The sweep reaches every address in the database roughly once every 12 hours.
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 200,835 endpoints that stopped working.
Middle halfMedianFull range
How quickly one answers
Response time on the last successful check, across the 10,506 proxies answering right now.
Continuous monitoring
How HProxy checks 134.35.10.155:8080
HProxy has checked 134.35.10.155:8080 224 times and it answered 1 of those. Every one of those was a real connection attempt, never a lookup.
9 public sources published it
134.35.10.155 appears in 9 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 8080: HTTP, alternate
Port 8080 is the most common proxy port on the internet. It stands in for port 80, and unlike port 80 any program can open it without administrator rights. That single detail is why so much ends up here, the deliberate and the accidental alike.
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 134.35.10.155:8080 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, so a proxy is never missed because we guessed the wrong protocol.
224 checks, 1 answered
That is 0% of the time, measured since June 7, 2026. Every one of those results, successes and failures alike, is a connection HProxy opened itself.
We are still watching for it to come back
Being archived does not stop the testing. 134.35.10.155:8080 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 12 hours. Its last check was on August 31, 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 134.35.10.155:8080, and nothing it does not.
- First seen
- June 7, 2026
- Last checked
- August 31, 2026
- Next check due
- within 12 hours
- Checks run
- 224
- Times it answered
- 1
- Stopped answering
- July 22, 2026
0%
answered 1 of 224 checks
Live free proxies right now
View all
Where this address sits
Right now our free pool holds no other free proxies on PTC-YemenNet, and 7 in Yemen. 134.35.10.155:8080 sits inside that set, so if it is not usable the pages below are where its closest alternatives are.
PTC-YemenNet is the 77th 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 652 addresses on AS30873, which is 0.09% of every address in the database and a small corner of the database. That makes it the 77th largest source of free proxies of every network we have ever seen. None of them are answering at the moment, though every one stays in the re-check rotation in case that changes.
- Answered before19%
- Never answered81%
- 1LimitedNetwork-ASAS213790227,474
- 2SECURED SERVERS LLCAS1943745,247
- 3Amazon.com, Inc.AS1650935,163
- 4SECURED SERVERS LLCAS2045429,141
- 5Cloudflare, Inc.AS1333522,886
- 6M247AS900915,997
- 7Cloudflare, Inc.AS20924214,257
- 8Alibaba (US) Technology Co., Ltd.AS4510212,165
68 networks between
77PTC-YemenNetAS30873652
Questions about 134.35.10.155:8080
Is 134.35.10.155:8080 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 July 22, 2026. We still re-test it periodically in case it returns.
Was 134.35.10.155 ever actually a proxy?
Yes. We ran 224 checks against it and it answered 1 of them, about 0% of the time, over 45 days on our list.
What is the hostname for 134.35.10.155?
134.35.10.155 publishes no reverse DNS record. That is not unusual and it is not suspicious on its own, but it does mean the address volunteers nothing about who runs it, so the network and the check history below are all there is to go on.
Where was 134.35.10.155 hosted?
Sanaa, Amanat Alasimah, Yemen, PTC-YemenNet (AS30873). 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 PTC-YemenNet?
None other than 134.35.10.155:8080 at the moment. AS30873 (PTC-YemenNet) has no other free proxies live in our pool right now, though that changes as we re-verify.
Are there other free proxies in Yemen?
Yes, 7 free proxies are exiting from Yemen in our pool right now. 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
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.