| # | Proxy (IP:Port) | Protocol | HTTPS | Country | Anonymity | Latency | Uptime (7d) | Last checked |
|---|---|---|---|---|---|---|---|---|
| 1 | 45.65.138.48:999 | http | ✓ TLS | Colombia / Villa del Rosario | elite | 4187 ms | 76.97% | 1h ago |
| 2 | 45.65.137.218:999 | http | ✓ TLS | Colombia / Villa del Rosario | elite | 2035 ms | 76.04% | 2m ago |
| 3 | 181.236.221.138:4145 | socks4 | — | Colombia / Girón | elite | 2696 ms | 65.98% | 2m ago |
| 4 | 186.96.111.214:999 | http | ✓ TLS | Colombia / Granada | elite | 10764 ms | 58.79% | 23m ago |
| 5 | 38.50.39.51:999 | http | ✓ TLS | Colombia / Bogotá | elite | 8477 ms | 34.52% | 2h ago |
| 6 | 179.1.126.25:999 | http | ✓ TLS | Colombia / Quibdó | elite | 9937 ms | 20% | 1h ago |
| 7 | 181.78.17.131:999 | http | ✓ TLS | Colombia / Andalucía | elite | 9657 ms | 43.2% | 23h ago |
| 8 | 190.60.58.236:999 | http | ✓ TLS | Colombia / Madrid | elite | 4082 ms | 32.31% | 1d ago |
| 9 | 181.143.42.138:8080 | http | ✓ TLS | Colombia / Medellín | elite | 9182 ms | 33.64% | 27m ago |
| 10 | 38.191.194.27:999 | http | ✓ TLS | Colombia / Cali | elite | 9519 ms | 45.61% | 59m ago |
| 11 | 181.225.96.137:999 | http | ✓ TLS | Colombia / Bogotá | elite | 6397 ms | 6.25% | 13h ago |
| 12 | 190.61.43.117:8080 | http | ✓ TLS | Colombia / Santa Marta | elite | 9110 ms | 21.43% | 22m ago |
| 13 | 190.109.6.115:999 | http | ✓ TLS | Colombia / Tocancipá | elite | 6415 ms | 16.67% | 6h ago |
| 14 | 190.61.40.85:999 | http | ✓ TLS | Colombia / Pueblorrico | elite | 6528 ms | 15.15% | 9h ago |
| 15 | 190.109.6.113:999 | http | ✓ TLS | Colombia / Tocancipá | elite | 6166 ms | 5.88% | 4h ago |
| 16 | 131.100.51.145:999 | http | ✓ TLS | Colombia / Florencia | elite | 5116 ms | 10% | 9h ago |
| 17 | 179.1.48.48:8080 | http | ✓ TLS | Colombia / Cali | elite | 7281 ms | 29.23% | 42m ago |
| 18 | 190.144.238.66:8080 | http | ✓ TLS | Colombia / Buenos Aires | elite | 6461 ms | 19.64% | 2h ago |
| 19 | 190.14.224.244:999 | http | ✓ TLS | Colombia / Buenos Aires | elite | 5011 ms | 18.52% | 3h ago |
| 20 | 177.73.155.246:999 | http | ✓ TLS | Colombia / Piendamo | elite | 10464 ms | 29.63% | 54s ago |
| 21 | 181.129.183.19:53281 | http | ✓ TLS | Colombia / Bucaramanga | elite | 5228 ms | 51.63% | 29m ago |
| 22 | 38.211.76.17:999 | http | ✓ TLS | Colombia / Florencia | elite | 10737 ms | 27.94% | 1h ago |
| 23 | 179.1.131.129:8080 | http | ✓ TLS | Colombia / Cúcuta | elite | 8892 ms | 23.53% | 6h ago |
| 24 | 64.204.90.177:999 | http | ✓ TLS | Colombia / Ocaña | elite | 3833 ms | 31.3% | 3h ago |
| 25 | 38.19.43.108:999 | http | ✓ TLS | Colombia / Bogotá | elite | 5559 ms | 35.94% | 4h ago |
| 26 | 181.225.73.104:999 | http | ✓ TLS | Colombia / Bogotá | elite | 8888 ms | 16.67% | 13h ago |
| 27 | 177.93.48.137:999 | http | ✓ TLS | Colombia / Bogotá | elite | 7367 ms | 7.41% | 4h ago |
| 28 | 190.109.6.121:999 | http | ✓ TLS | Colombia / Tocancipá | elite | 4261 ms | 8% | 1h ago |
| 29 | 186.1.182.194:4153 | socks4 | ✓ TLS | Colombia / Santa Marta | elite | 3790 ms | 59.9% | 3m ago |
| 30 | 138.117.85.217:999 | http | ✓ TLS | Colombia / Garzón | elite | 1958 ms | 23.53% | 45m ago |
| 31 | 38.41.0.87:999 | http | ✓ TLS | Colombia / Cúcuta | elite | 8033 ms | 31.72% | 37m ago |
| 32 | 24.152.58.107:999 | http | ✓ TLS | Colombia / Floridablanca | elite | 3114 ms | 33.33% | 4h ago |
| 33 | 179.1.182.20:999 | http | ✓ TLS | Colombia / Aipe | elite | 6803 ms | 32.88% | 1d ago |
| 34 | 200.10.30.5:8083 | http | ✓ TLS | Colombia / Pereira | elite | 9275 ms | 36.84% | 50m ago |
| 35 | 190.61.61.210:999 | http | ✓ TLS | Colombia / Villapinzón | elite | 5455 ms | 33.8% | 12m ago |
| 36 | 24.152.58.22:999 | http | ✓ TLS | Colombia / Floridablanca | elite | 8804 ms | 32.94% | 5h ago |
| 37 | 186.180.20.18:8080 | http | ✓ TLS | Colombia / Bogotá | elite | 7248 ms | 39.46% | 16m ago |
| 38 | 181.119.84.134:8080 | http | ✓ TLS | Colombia / Cali | elite | 7364 ms | 27.78% | 4h ago |
| 39 | 190.109.1.58:8080 | http | ✓ TLS | Colombia / Bogotá | elite | 5203 ms | 39.34% | 5h ago |
| 40 | 24.152.58.100:999 | http | ✓ TLS | Colombia / Bogotá | elite | 7712 ms | 26.47% | 10h ago |
| 41 | 38.191.212.81:999 | http | ✓ TLS | Colombia / Cúcuta | elite | 2552 ms | 27.03% | 2h ago |
| 42 | 38.191.200.244:999 | http | ✓ TLS | Colombia / Bogotá | elite | 9108 ms | 6.25% | 4h ago |
| 43 | 190.26.209.126:999 | http | ✓ TLS | Colombia / Granada | elite | 9090 ms | 31.82% | 31m ago |
| 44 | 190.99.192.158:999 | http | ✓ TLS | Colombia / Cali | elite | 9016 ms | 38% | 4h ago |
| 45 | 38.19.238.5:999 | http | ✓ TLS | Colombia / Riosucio | elite | 7483 ms | 23.33% | 3h ago |
| 46 | 190.14.249.111:8080 | http | ✓ TLS | Colombia / Bogotá | elite | 5588 ms | 33.33% | 1h ago |
| 47 | 170.239.205.31:999 | http | ✓ TLS | Colombia / Bogotá | elite | 4519 ms | 35.09% | 45m ago |
| 48 | 24.152.58.99:999 | http | ✓ TLS | Colombia / Bogotá | elite | 4779 ms | 15.79% | 1h ago |
| 49 | 191.103.219.225:48612 | http | — | Colombia / Tolú | elite | 8043 ms | 22.45% | 2h ago |
| 50 | 181.119.67.156:999 | http | ✓ TLS | Colombia / Bogotá | elite | 2943 ms | 15% | 1d ago |
A quick automated human-verification check runs before more proxies load. We don't offer bulk download or an API — this list is for manual use.
Browse proxies by country
Use public proxies with caution. These are open, third-party servers we did not set up. A working proxy can still log your traffic, inject content, or expose your real IP through DNS, WebRTC, or application headers.
Never send passwords, financial data, or other sensitive traffic through an untrusted proxy. Verify a proxy with our Proxy Tester before relying on it, and only use proxies where you are authorized to do so.
ℹ️ About Colombia Proxy List
What is this free proxy list?
This page publishes a live list of public HTTP, HTTPS, SOCKS4, and SOCKS5 proxy servers drawn from our continuously monitored proxy database. Every proxy is re-tested on a short interval by a distributed worker fleet, so the status, latency, anonymity level, and geographic location reflect recent checks rather than a stale dump. Only proxies that are currently alive are listed, and credentialed/private proxies are never published.
The first 50 results load instantly. To reveal the rest (up to 200) a lightweight, invisible human-verification check runs first — this keeps the list useful for people while discouraging automated bulk scraping. There is intentionally no bulk download or public API.
HTTP vs HTTPS vs SOCKS proxies
- HTTP — forwards plain HTTP requests; best for simple web traffic and scraping non-TLS endpoints.
- HTTPS — supports the
CONNECTmethod to tunnel TLS, so it can carry encryptedhttps://traffic. - SOCKS4 — a lower-level TCP tunnel; no authentication of the proxied protocol and no UDP/IPv6.
- SOCKS5 — the most flexible: TCP and UDP, IPv6, and optional auth. Defined in RFC 1928. HTTP semantics are defined in RFC 9110 and the standardized forwarding header in RFC 7239.
The HTTPS column (✓ TLS) marks proxies we verified can tunnel encrypted https:// traffic — confirmed either by a live TLS probe or by the proxy reaching our HTTPS test endpoint. This is independent of the proxy's own scheme: an HTTP-listed proxy can still be HTTPS-capable via CONNECT. Use the HTTPS filter to show only TLS-capable proxies.
Anonymity levels & safety ratings
| Level | Reveals your IP? | Privacy rating | Use |
|---|---|---|---|
| Elite | No — and hides that a proxy is used | Strongest | Best choice for anonymity |
| Anonymous | No, but reveals a proxy is in use | Medium | OK for general use |
| Transparent | Yes — forwards your real IP | None | Caching/testing only, not privacy |
How "reliability" and uptime are measured
The default sort ranks proxies by recent success streak. The Uptime (7d) column is the share of our last week of checks that succeeded for that proxy. Latency is the most recent measured round-trip time. Because public proxies are volatile, a proxy that is up now may be down within hours — re-verify before depending on it.