Skip to contentPeru: free public proxies 🇵🇪
Peru: 15 public proxies marked working in this snapshot. The table also includes check history; recheck before use.
showing 1–60 of 122 (working first, then history)
Rows marked “not working” are excluded from the working count. History retains recorded entries; a last-response time is shown when known.
| 999 | HTTP | 🇵🇪Puno | Transparent | – | 199 ms | 100% | ||
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 182 ms | 100% | ||
| 999 | HTTP | 🇵🇪Sauce | Transparent | – | 184 ms | 99% | ||
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 191 ms | 98% | ||
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 1403 ms | 57% | ||
| 999 | HTTP | 🇵🇪Pozuzo | Transparent | – | 5850 ms | 42% | ||
| 8080 | HTTP | 🇵🇪La Quebrada | Transparent | – | 4932 ms | 38% | ||
| 8080 | HTTPS | 🇵🇪La Quebrada | Transparent | ✓ | 3495 ms | 35% | ||
| 999 | HTTPS | 🇵🇪Cusco | Transparent | ✓ | 6501 ms | 34% | ||
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 8194 ms | 31% | ||
| 999 | HTTPS | 🇵🇪Pozuzo | Transparent | ✓ | 3309 ms | 30% | ||
| 999 | HTTP | 🇵🇪Arequipa | Transparent | – | 4444 ms | 26% | ||
| 999 | HTTPS | 🇵🇪Puno | Transparent | ✓ | 8377 ms | 22% | ||
| 999 | HTTPS | 🇵🇪Arequipa | Transparent | ✓ | 4037 ms | 16% | ||
| Private connection options Compare authenticated SOCKS5/HTTP and optional dedicated IP plans. Check the service terms; availability can vary. See s4m Proxy → | ||||||||
| 999 | HTTPS | 🇵🇪Huaura | Transparent | ✓ | 4249 ms | 12% | ||
| 999 | HTTPS | 🇵🇪Satipo | Transparent | ✓ | 181 ms | 51% | not working last alive | |
| 999 | HTTP | 🇵🇪Cusco | Transparent | – | 198 ms | 49% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 171 ms | 49% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 188 ms | 49% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 171 ms | 49% | not working last alive | |
| 8443 | HTTPS | 🇵🇪San Francisco De Borja | Transparent | ✓ | 200 ms | 49% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 197 ms | 49% | not working last alive | |
| 999 | HTTPS | 🇵🇪Cusco | Transparent | ✓ | 199 ms | 49% | not working last alive | |
| 1083 | HTTP | 🇵🇪Tucsipampa | Elite | – | 189 ms | 48% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 180 ms | 48% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 5669 ms | 48% | not working last alive | |
| 5678 | SOCKS4 | 🇵🇪Lima | Elite | – | 187 ms | 48% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 181 ms | 47% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 186 ms | 46% | not working last alive | |
| 1080 | SOCKS4 | 🇵🇪Ayacucho | Elite | – | 184 ms | 46% | not working last alive | |
| 8080 | HTTP | 🇵🇪Morales | Transparent | – | 191 ms | 46% | not working last alive | |
| 999 | HTTPS | 🇵🇪Lima | Transparent | ✓ | 175 ms | 46% | not working last alive | |
| 999 | HTTPS | 🇵🇪Lima | Transparent | ✓ | 189 ms | 46% | not working last alive | |
| 8080 | HTTP | 🇵🇪Arequipa | Transparent | – | 4654 ms | 46% | not working last alive | |
| 8443 | HTTP | 🇵🇪Lima | Transparent | – | 208 ms | 45% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 186 ms | 45% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 182 ms | 45% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 196 ms | 45% | not working last alive | |
| 999 | HTTP | 🇵🇪Cusco | Transparent | – | 193 ms | 44% | not working last alive | |
| 1084 | HTTP | 🇵🇪Tucsipampa | Elite | – | 184 ms | 44% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 184 ms | 43% | not working last alive | |
| 999 | HTTPS | 🇵🇪Lima | Transparent | ✓ | 185 ms | 43% | not working last alive | |
| 999 | HTTPS | 🇵🇪Lima | Transparent | ✓ | 204 ms | 43% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 194 ms | 43% | not working last alive | |
| 999 | HTTPS | 🇵🇪San Ramón | Transparent | ✓ | 191 ms | 42% | not working last alive | |
| 999 | HTTPS | 🇵🇪Lima | Transparent | ✓ | 5401 ms | 42% | not working last alive | |
| 8080 | HTTP | 🇵🇪Ayacucho | Transparent | – | 189 ms | 42% | not working last alive | |
| 1080 | SOCKS4 | 🇵🇪Ayacucho | Elite | – | 189 ms | 41% | not working last alive | |
| 999 | HTTP | 🇵🇪Satipo | Transparent | – | 6494 ms | 41% | not working last alive | |
| 999 | HTTPS | 🇵🇪Lima | Transparent | ✓ | 208 ms | 40% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 182 ms | 39% | not working last alive | |
| 999 | HTTP | 🇵🇪Ayacucho | Transparent | – | 184 ms | 37% | not working last alive | |
| 999 | HTTP | 🇵🇪Cusco | Transparent | – | 4445 ms | 35% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 4693 ms | 34% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 188 ms | 33% | not working last alive | |
| 8080 | HTTPS | 🇵🇪Arequipa | Transparent | ✓ | 197 ms | 33% | not working last alive | |
| 999 | HTTPS | 🇵🇪Lima | Transparent | ✓ | 6130 ms | 31% | not working last alive | |
| 1083 | HTTPS | 🇵🇪Tucsipampa | Elite | ✓ | 5404 ms | 31% | not working last alive | |
| 8443 | HTTPS | 🇵🇪Lima | Transparent | ✓ | 4966 ms | 31% | not working last alive | |
| 999 | HTTPS | 🇵🇪Arequipa | Transparent | ✓ | 8707 ms | 31% | not working last alive | |
These are public, unverified third-party proxies — use at your own risk and never send sensitive traffic through them. For reliable, private proxies see s4m Proxy.
At a glance
This page has 15 entries marked working. Mean recorded check success across these entries is 49%; mean recorded response time, where available, is 3703 ms. By protocol: HTTP (9), HTTPS (6). By anonymity level: Transparent (15). The most common ports are 999, 8080. Measurements come from recorded checks, not a promise of availability. Use ⟳ to recheck before use.
This catalogue groups public proxy records under Peru. Country and anonymity labels are catalogue metadata, not verified operator identity or a privacy guarantee. Check the protocol and recorded times, then recheck before use. Do not send sensitive traffic through public proxies.
For authenticated access, compare private SOCKS5/HTTP, WireGuard VPN and optional dedicated IP plans. Read VPN vs proxy, the privacy policy and service terms. Availability can vary; public proxies remain unverified.
Free proxies — FAQ
How often is this free proxy list checked?
Scheduled checks record reachability and response time. The working mark follows the catalogue's retry policy and can differ from the latest attempt. Failed entries may remain as history. Use the shown timestamps and recheck; a fixed interval or continued availability is not guaranteed.
Are free public proxies safe to use?
Public proxy operators are unverified third parties. Do not send credentials or sensitive traffic through them. An elite label does not certify privacy, encryption or logging policy. A private proxy or VPN also requires a separate assessment of the provider.
How do I use a proxy from this list?
Choose the matching protocol and configure the shown IP:port in your client. For HTTP, curl -x http://IP:PORT https://api.ipify.org checks that request's exit IP. Recheck first; this does not test DNS, WebRTC or provider logging.
Private connection options
Compare authenticated SOCKS5/HTTP and optional dedicated IP plans. Check the service terms; availability can vary.
Explore s4m Proxy →People found this page by searching for
- Peru
- SOCKS5 & HTTP proxies
- Peru ip address
- free proxies Peru
- anonymous proxies Peru
- how to set up elite proxies
- free proxy list
- dedicated ip for android
- elite proxy list
- free proxy list
- free proxies
- working proxies tutorial
- is proxy list safe
Real search phrases this page answers — the linked ones open the page that covers them in depth.