Is 206.135.45.237:999 a proxy? It was listed.
206.135.45.237:999 was listed as a public proxy in 1 of our sources. Since June 6, 2026 we have tried it 145 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.
MexicoHow this one compares
145 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 145 times, which is why the answer on this page is a flat no rather than a maybe.
0%
of 145 checks answered
Pool median 34.6%. 206.135.45.237:999 sits below it, which is ordinary for a public proxy.
145
real connection attempts
Each one opens a socket and waits up to 90 seconds. Slow and unreachable look identical if you stop listening early.
8
days in our records, never once answering
It is not in the lifespan figures at all: those cover the 397,390 endpoints that worked at least once before they stopped.
June 6, 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.
October 15, 2026
Most recent re-test
HProxy has opened 145 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 397,390 endpoints that stopped working.
Middle halfMedianFull range
How quickly one answers
Response time on the last successful check, across the 5,637 proxies answering right now.
Continuous monitoring
How HProxy checks 206.135.45.237:999
HProxy has opened a connection to 206.135.45.237:999 145 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
206.135.45.237 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 999: System port
Ports below 1024 are protected. On most systems you need administrator rights to open one at all. So whatever is answering here was set up by someone with full control of that machine, not by some ordinary program that happened to be running.
Every failure here was measured, not assumed
Each check opens a real connection to 206.135.45.237:999 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. 145 times HProxy tried, and 145 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.
145 checks, zero connections
Not one of those 145 attempts reached a working proxy. The address stays in the database with that result attached, because "we tried 145 times and it never answered" is a far more useful answer than silence for anyone who found 206.135.45.237 somewhere and wants to know what it is.
It is still re-tested every 12 hours
206.135.45.237:999 has never answered, and it is still in the rotation anyway. The sweep reaches every address in the database roughly once every 12 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 October 15, 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 206.135.45.237:999, and nothing it does not.
- First seen
- June 6, 2026
- Last checked
- October 15, 2026
- Next check due
- within 12 hours
- Checks run
- 145
- Times it answered
- 0
- Stopped answering
- June 14, 2026
0%
never answered across 145 attempts
Live free proxies right now
View all
Where this address sits
Right now our free pool holds 12 other free proxies on GTT, and 522 in Mexico. 206.135.45.237:999 sits inside that set, so if it is not usable the pages below are where its closest alternatives are.
GTT is the 55th 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,176 addresses on AS3257, which is 0.13% of every address in the database and a meaningful pocket of the database. That makes it the 55th largest source of free proxies of every network we have ever seen. 12 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 now1%
- Answered before36%
- Never answered63%
- 1LimitedNetwork-ASAS213790227,474
- 2SECURED SERVERS LLCAS19437120,032
- 3M247AS900982,399
- 4SECURED SERVERS LLCAS2045456,868
- 5Amazon.com, Inc.AS1650950,169
- 6Cloudflare, Inc.AS1333522,933
- 7Cloudflare, Inc.AS20924214,281
- 8Alibaba (US) Technology Co., Ltd.AS4510212,395
46 networks between
55GTTAS32571,176
Questions about 206.135.45.237:999
Is 206.135.45.237:999 a working proxy?
Not for us. 206.135.45.237:999 was published as a public proxy by our sources, and across 145 checks since June 6, 2026 it has never answered.
Was 206.135.45.237 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 June 6, 2026, and across 145 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 206.135.45.237?
Its reverse DNS record is 206-135-45-237.customer.ientc.net.mx. That is what the address itself publishes about who operates it, which is often more telling than the network name: hosting providers name their machines by region and instance type, and a residential line usually carries its ISP's own pattern.
Where was 206.135.45.237 hosted?
Tlalixcoyan, Veracruz, Mexico, GTT (AS3257). 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 GTT?
12 other free proxies are live on GTT (AS3257) in our pool right now, alongside 206.135.45.237:999. 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 Mexico?
Yes, 522 free proxies are exiting from Mexico in our pool right now, answering in 4508ms 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.