How this one compares
2 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 2 times, which is why the answer on this page is a flat no rather than a maybe.
0%
of 2 checks answered
Pool median 26%. 86.38.26.232:6397 sits below it, which is ordinary for a public proxy.
2
real connection attempts
Each one opens a socket and waits up to 90 seconds. Slow and unreachable look identical if you stop listening early.
0
days in our records, never once answering
It is not in the lifespan figures at all: those cover the 272,239 endpoints that worked at least once before they stopped.
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 272,239 endpoints that stopped working.
Middle halfMedianFull range
How quickly one answers
Response time on the last successful check, across the 6,167 proxies answering right now.
Where this address sits
Right now our free pool holds no other free proxies on BITE-US, and 8 in Lithuania. 86.38.26.232:6397 sits inside that set, so if it is not usable the pages below are where its closest alternatives are.
BITE-US is the 58th 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 1,020 addresses on AS210906, which is 0.13% of every address in the database and a meaningful pocket of the database. That makes it the 58th 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.
- Never answered100%
- 1LimitedNetwork-ASAS213790227,474
- 2SECURED SERVERS LLCAS1943779,187
- 3SECURED SERVERS LLCAS2045447,197
- 4Amazon.com, Inc.AS1650944,504
- 5Cloudflare, Inc.AS1333522,924
- 6M247AS900919,105
- 7Cloudflare, Inc.AS20924214,275
- 8Alibaba (US) Technology Co., Ltd.AS4510212,248
49 networks between
58BITE-USAS2109061,020
How to use this proxy
Route a request through 86.38.26.232:6397 over HTTP. Free proxies are shared and rotate out fast, so test before you rely on it.
curl -x http://86.38.26.232:6397 \
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 86.38.26.232:6397
86.38.26.232:6397 is in the live pool right now, and it stays there only for as long as it keeps answering.
Port 6397: 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 failure here was measured, not assumed
Each check opens a real connection to 86.38.26.232:6397 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. Nothing about this record is inherited from the list that published the address. 2 times HProxy tried, and 2 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, which is how we know it spoke HTTP.
2 checks, zero connections
Not one of those 2 attempts reached a working proxy. The address stays in the database with that result attached, because "we tried 2 times and it never answered" is a far more useful answer than silence for anyone who found 86.38.26.232 somewhere and wants to know what it is.
It is being re-tested continuously
86.38.26.232:6397 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 86.38.26.232:6397, and nothing it does not.
- First seen
- September 12, 2026
- Last checked
- September 12, 2026
- Next check due
- continuously
- Checks run
- 2
- Times it answered
- 0
- Spoke
- HTTP
0%
never answered across 2 attempts
Questions about 86.38.26.232:6397
Is 86.38.26.232:6397 a working proxy right now?
Yes. 86.38.26.232:6397 answered HProxy's automated check now 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 86.38.26.232?
It speaks HTTP. The port is 6397. Point your client at 86.38.26.232:6397 over http to route a request through it.
Where is 86.38.26.232 located?
Traffic through it exits from Lithuania, on BITE-US (AS210906). That is where the destination site will think your request came from.
How reliable has 86.38.26.232:6397 been?
Across 1 day of tracking it answered 0% 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 86.38.26.232:6397?
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 BITE-US?
None other than 86.38.26.232:6397 at the moment. AS210906 (BITE-US) has no other free proxies live in our pool right now, though that changes as we re-verify.
Are there other free proxies in Lithuania?
Yes, 8 free proxies are exiting from Lithuania in our pool right now, answering in 2541ms 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.
86.38.26.232:6397 answers 0% 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 all
78.63.115.20:8899
SOCKS5 · Lithuania · 13% · 243ms
212.24.108.20:11920
HTTP · Lithuania · 12% · 308ms
93.93.61.153:1080
SOCKS4 · Lithuania · 25% · 2475ms
194.135.81.158:3128
HTTP · Lithuania · 37% · 2541ms
88.119.139.237:53281
HTTPS · Lithuania · 17% · 2671ms
213.197.136.218:5678
SOCKS4 · Lithuania · 28% · 7457ms
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.