Is 138.121.113.12:8787 a proxy? Yes.
138.121.113.12:8787 is a public HTTP proxy in the HProxy free proxy list, exiting from Argentina. It holds a moderate 60% uptime with a high 4583ms response time, and last answered our checker 12 min ago.
uptime
How this one compares
Reliable enough to sit in the better half of everything we are watching.
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,908 proxies answering right now, the middle of the pack answers 39.6% of the checks we send it.
60%
of 4,267 checks answered
Pool median 39.6%. 138.121.113.12:8787 is in the better half.
4583ms
on its last response
Pool median 4,961ms.
70
days tracked, still in the live pool
Of the 438,644 free proxies we have watched stop working, half were gone within 21 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 438,644 endpoints that stopped working.
Middle halfMedianFull range
How quickly one answers
Response time on the last successful check, across the 6,908 proxies answering right now.
Where this address sits
Right now our free pool holds 1 other free proxy on Refsa Telecomunicaciones, and 229 in Argentina. 138.121.113.12:8787 sits inside that set, so if it is not usable the pages below are where its closest alternatives are. At 4583ms it answers faster than the 4899ms median for Argentina proxies (about 94% of it).
How many free proxies are on REFSA TELECOMUNICACIONES
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 8 addresses on AS263791, which is 0.00% of every address in the database and a small corner of the database. 2 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 now25%
- Answered before25%
- Never answered50%
- 1LimitedNetwork-ASAS213790227,474
- 2SECURED SERVERS LLCAS19437120,032
- 3M247AS900999,643
- 4Amazon.com, Inc.AS1650958,890
- 5SECURED SERVERS LLCAS2045456,868
- 6Cloudflare, Inc.AS1333522,945
- 7Cloudflare, Inc.AS20924214,287
- 8Alibaba (US) Technology Co., Ltd.AS4510212,499
- AS263791 sits outside the 250 largest networks we hold.
How to use this proxy
Route a request through 138.121.113.12:8787 over HTTP. Free proxies are shared and rotate out fast, so test before you rely on it.
curl -x http://138.121.113.12:8787 \
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 138.121.113.12:8787
138.121.113.12:8787 is in the live pool right now, and it stays there only for as long as it keeps answering.
Port 8787: Registered port range
This port sits in the middle range, where any ordinary program can listen without special permission. The number itself carries no reserved meaning, which tells you somebody picked it on purpose instead of accepting a 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 a real connection to 138.121.113.12:8787 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.
4,267 checks, 2,574 answered
That is 60% of the time, measured since September 3, 2026. Every one of those results, successes and failures alike, is a connection HProxy opened itself.
It is being re-tested continuously
138.121.113.12:8787 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 138.121.113.12:8787, and nothing it does not.
- First seen
- September 3, 2026
- Last checked
- November 12, 2026
- Next check due
- continuously
- Checks run
- 4,267
- Times it answered
- 2,574
- Spoke
- HTTP, HTTPS
60%
answered 2,574 of 4,267 checks
Questions about 138.121.113.12:8787
Is 138.121.113.12:8787 a working proxy right now?
Yes. 138.121.113.12:8787 answered HProxy's automated check 12 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 138.121.113.12?
It speaks HTTP, HTTPS, and our checks grade it elite. The port is 8787. Point your client at 138.121.113.12:8787 over http to route a request through it.
Where is 138.121.113.12 located?
Traffic through it exits from Formosa, Argentina, on REFSA TELECOMUNICACIONES (AS263791). That is where the destination site will think your request came from.
How fast is 138.121.113.12:8787?
It answered in 4583ms 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 138.121.113.12:8787 been?
Across 71 days of tracking it answered 60% 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 138.121.113.12:8787?
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 Refsa Telecomunicaciones?
1 other free proxy is live on Refsa Telecomunicaciones (AS263791) in our pool right now, alongside 138.121.113.12:8787. 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 Argentina?
Yes, 229 free proxies are exiting from Argentina in our pool right now, answering in 4899ms 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.
138.121.113.12:8787 answers 60% 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 all138.121.113.179:999
HTTP · Argentina · 39% · 8333ms
190.111.243.150:1085
SOCKS4 · Argentina · 25% · 546ms
190.228.33.44:1085
SOCKS4 · Argentina · 19% · 621ms
200.122.92.211:5678
SOCKS4 · Argentina · 29% · 673ms
170.79.182.202:3389
SOCKS4 · Argentina · 5% · 721ms
190.220.1.173:35376
SOCKS4 · Argentina · 28% · 730ms
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.