Is 104.129.192.156:10300 a proxy? Yes.
104.129.192.156:10300 is a public HTTP proxy in the HProxy free proxy list, exiting from United States. It holds a moderate 73% uptime with a high 29468ms response time, and was last checked 14 min ago.
uptime
Uptime & downtime
7
Days tracked
432
Checks run
53.5%
Downtime
7
Down days
Continuous monitoring
How HProxy checks 104.129.192.156:10300
104.129.192.156:10300 is in the live pool right now, and it stays there only for as long as it keeps answering. Here is exactly what HProxy does to it, and how often.
Port 10300: Registered port range
This port sits in the registered range, which any user-level program may listen on without special rights. It carries no reserved meaning of its own, so the number tells you the proxy was configured deliberately on a chosen port rather than on a system default.
Every check is a real connection
HProxy does not read this address off somebody else's list and pass it on. Each check opens an actual connection to 104.129.192.156:10300 and waits up to 4 seconds for the other end to complete a proxy handshake. 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.
1,815 checks, 1,323 answered
That is 73% of the time, measured since July 7, 2026. Every one of those results, successes and failures alike, is a connection HProxy opened itself.
It is being re-tested continuously
104.129.192.156:10300 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 104.129.192.156:10300, and nothing it does not.
- First seen
- July 7, 2026
- Last checked
- August 3, 2026
- Next check due
- continuously
- Checks run
- 1,815
- Times it answered
- 1,323
- Spoke
- HTTP
73%
answered 1,323 of 1,815 checks
How to use this proxy
Route a request through 104.129.192.156:10300 over HTTP. Free proxies are shared and rotate out fast, so test before you rely on it.
curl -x http://104.129.192.156:10300 \
https://api.ipify.org?format=json
Other live free proxies
View all →Where this address sits
Right now our free pool holds 68 other free proxies on Zscaler, and 1,049 in United States. 104.129.192.156:10300 sits inside that set, so if it is not usable the pages below are where its closest alternatives are. At 29468ms it is slower than the 2520ms median for United States proxies.
What HProxy holds on ZSCALER, INC.
Open proxies are not spread evenly across the internet. They cluster, because one misconfigured template, one cheap hosting reseller or one leaked image tends to produce hundreds of identical machines on the same network. HProxy tracks 330 addresses on AS22616, which is 0.06% of every address in the database and a small corner of the database. 280 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 now85%
- Answered before9%
- Never answered6%
Questions about 104.129.192.156:10300
Is 104.129.192.156:10300 a working proxy right now?
Yes. 104.129.192.156:10300 answered HProxy's automated check 14 min 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 104.129.192.156?
It speaks HTTP, and our checks grade it elite. The port is 10300. Point your client at 104.129.192.156:10300 over http to route a request through it.
Where is 104.129.192.156 located?
Traffic through it exits from San Jose, United States, on ZSCALER, INC. (AS22616). That is where the destination site will think your request came from.
How fast is 104.129.192.156:10300?
It answered in 29468ms 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 104.129.192.156:10300 been?
Across 28 days of tracking it answered 73% 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 104.129.192.156:10300?
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 Zscaler?
68 other free proxies are live on Zscaler (AS22616) in our pool right now, alongside 104.129.192.156:10300. 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 United States?
Yes, 1,049 free proxies are exiting from United States in our pool right now, answering in 2520ms 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
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.