Is 134.35.146.167:8080 a proxy? It was listed.
134.35.146.167:8080 was listed as a public proxy in 1 of our sources. Since May 21, 2026 we have tried it 98 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.
never answered us
YemenHow this one compares
98 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 98 times, which is why the answer on this page is a flat no rather than a maybe.
0%
of 98 checks answered
Pool median 15.4%. 134.35.146.167:8080 sits below it, which is ordinary for a public proxy.
98
real connection attempts
Each one opens a socket and waits up to 90 seconds. Slow and dead look identical if you stop listening early.
24
days in our records, never once answering
It is not in the lifespan figures at all: those cover the 192,523 endpoints that worked at least once before they stopped.
May 21, 2026
First listed by our sources
Published as a working proxy by 1 of the public lists HProxy tracks. Being listed is a claim, not a test.
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.
August 10, 2026
Most recent re-test
HProxy has opened 98 real connections to this endpoint in total. The sweep reaches every address in the database roughly once every 24 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 192,523 endpoints that stopped working.
Middle halfMedianFull range
How quickly one answers
Response time on the last successful check, across the 4,589 proxies answering right now.
Continuous monitoring
How HProxy checks 134.35.146.167:8080
HProxy has opened a connection to 134.35.146.167:8080 98 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.
One public source published it
134.35.146.167 reached HProxy through a single public proxy source. Being published on a list is a claim that an address works. It is not a test, and nobody on that chain is obliged to have tried it.
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 failure here was measured, not assumed
Each check opens a real connection to 134.35.146.167:8080 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. 98 times HProxy tried, and 98 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.
98 checks, zero connections
Not one of those 98 attempts reached a working proxy. The address stays in the database with that result attached, because "we tried 98 times and it never answered" is a far more useful answer than silence for anyone who found 134.35.146.167 somewhere and wants to know what it is.
It is still re-tested every 24 hours
134.35.146.167:8080 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 134.35.146.167:8080, and nothing it does not.
- First seen
- May 21, 2026
- Last checked
- August 10, 2026
- Next check due
- within 24 hours
- Checks run
- 98
- Times it answered
- 0
- Stopped answering
- June 14, 2026
0%
never answered across 98 attempts
Live free proxies right now
View all →
Where this address sits
Right now our free pool holds 1 other free proxy on PTC-YemenNet, and none in Yemen. 134.35.146.167:8080 sits inside that set, so if it is not usable the pages below are where its closest alternatives are.
PTC-YemenNet is the 79th 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 579 addresses on AS30873, which is 0.10% of every address in the database and a small corner of the database. That makes it the 79th 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 before14%
- Never answered86%
- 1LimitedNetwork-ASAS213790227,266
- 2Amazon.com, Inc.AS1650925,965
- 3Cloudflare, Inc.AS1333522,185
- 4SECURED SERVERS LLCAS2045419,475
- 5Cloudflare, Inc.AS20924214,136
- 6Alibaba (US) Technology Co., Ltd.AS4510211,649
- 7GloboTech CommunicationsAS3666611,542
- 8ChinanetAS41348,359
70 networks between
79PTC-YemenNetAS30873579
Questions about 134.35.146.167:8080
Is 134.35.146.167:8080 a working proxy?
Not for us. 134.35.146.167:8080 was published as a public proxy by our sources, and across 98 checks since May 21, 2026 it has never answered.
Was 134.35.146.167 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 May 21, 2026, and across 98 checks since then it has never answered us. It was published 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.
What is the hostname for 134.35.146.167?
134.35.146.167 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.146.167 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?
1 other free proxy is live on PTC-YemenNet (AS30873) in our pool right now, alongside 134.35.146.167:8080. 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 Yemen?
Not at the moment. Yemen has no other free proxies live in our pool right now. The pool re-verifies constantly, so that number moves.
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.