Skip to contentPeru: free HTTP proxies 🇵🇪
Peru HTTP: 12 public proxies marked working in this snapshot. The table also includes check history; recheck before use.
showing 1–60 of 72 (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 | 🇵🇪San Roque de Cumbaza | Transparent | – | 188 ms | 99% | ||
| 999 | HTTP | 🇵🇪Tarma | Transparent | – | 175 ms | 99% | ||
| 1083 | HTTP | 🇵🇪Lima | Elite | – | 181 ms | 98% | ||
| 999 | HTTP | 🇵🇪Carhuacatac | Transparent | – | 178 ms | 98% | ||
| 999 | HTTP | 🇵🇪Cusco | Transparent | – | 198 ms | 98% | ||
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 5012 ms | 42% | ||
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 4027 ms | 41% | ||
| 999 | HTTP | 🇵🇪Arequipa | Transparent | – | 3133 ms | 28% | ||
| 8080 | HTTP | 🇵🇪Lima | Transparent | – | 2044 ms | 22% | ||
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 3848 ms | 17% | ||
| 999 | HTTP | 🇵🇪San Jerónimo | Transparent | – | 8026 ms | 16% | ||
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 6547 ms | 14% | ||
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 196 ms | 50% | not working last alive | |
| 999 | HTTP | 🇵🇪Chiclayo | Transparent | – | 192 ms | 50% | not working last alive | |
| Private connection options Compare authenticated SOCKS5/HTTP and optional dedicated IP plans. Check the service terms; availability can vary. See s4m Proxy → | ||||||||
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 195 ms | 49% | not working last alive | |
| 999 | HTTP | 🇵🇪Tarma | Transparent | – | 173 ms | 49% | not working last alive | |
| 3128 | HTTP | 🇵🇪Lima | Transparent | – | 187 ms | 48% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 178 ms | 48% | not working last alive | |
| 8080 | HTTP | 🇵🇪Arequipa | Transparent | – | 192 ms | 47% | not working last alive | |
| 999 | HTTP | 🇵🇪Tarma | Transparent | – | 176 ms | 47% | not working last alive | |
| 8080 | HTTP | 🇵🇪Tarapoto | Transparent | – | 191 ms | 46% | not working last alive | |
| 8443 | HTTP | 🇵🇪Quemazon | Transparent | – | 255 ms | 46% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 188 ms | 46% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 196 ms | 46% | not working last alive | |
| 1084 | HTTP | 🇵🇪Lima | Elite | – | 184 ms | 45% | not working last alive | |
| 999 | HTTP | 🇵🇪Puno | Transparent | – | 199 ms | 45% | not working last alive | |
| 999 | HTTP | 🇵🇪Acobamba | Transparent | – | 181 ms | 44% | not working last alive | |
| 999 | HTTP | 🇵🇪Cusco | Transparent | – | 193 ms | 44% | not working last alive | |
| 999 | HTTP | 🇵🇪Pozuzo | Transparent | – | 187 ms | 43% | not working last alive | |
| 8080 | HTTP | 🇵🇪Lima | Transparent | – | 188 ms | 43% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 179 ms | 43% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 194 ms | 42% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 182 ms | 42% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 2299 ms | 41% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 180 ms | 40% | not working last alive | |
| 8080 | HTTP | 🇵🇪Ayacucho | Transparent | – | 189 ms | 40% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 185 ms | 39% | not working last alive | |
| 999 | HTTP | 🇵🇪Ayacucho | Transparent | – | 184 ms | 39% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 185 ms | 38% | not working last alive | |
| 999 | HTTP | 🇵🇪Satipo | Transparent | – | 178 ms | 36% | not working last alive | |
| 999 | HTTP | 🇵🇪Ayacucho | Transparent | – | 189 ms | 32% | not working last alive | |
| 1081 | HTTP | 🇵🇪Lima | Elite | – | 179 ms | 32% | not working last alive | |
| 999 | HTTP | 🇵🇪Ayacucho | Transparent | – | 189 ms | 32% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 187 ms | 32% | not working last alive | |
| 999 | HTTP | 🇵🇪Sihuas | Transparent | – | 187 ms | 31% | not working last alive | |
| 999 | HTTP | 🇵🇪Arequipa | Transparent | – | 6971 ms | 30% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 184 ms | 29% | not working last alive | |
| 999 | HTTP | 🇵🇪Cusco | Transparent | – | 194 ms | 29% | not working last alive | |
| 999 | HTTP | 🇵🇪Arequipa | Transparent | – | 188 ms | 28% | not working last alive | |
| 999 | HTTP | 🇵🇪San Ramón | Transparent | – | 3997 ms | 28% | not working last alive | |
| 999 | HTTP | 🇵🇪Arequipa | Transparent | – | 3900 ms | 27% | not working last alive | |
| 999 | HTTP | 🇵🇪Arequipa | Transparent | – | 3397 ms | 27% | not working last alive | |
| 999 | HTTP | 🇵🇪Ayacucho | Transparent | – | 5290 ms | 21% | not working last alive | |
| 999 | HTTP | 🇵🇪San Ramón | Transparent | – | 8202 ms | 20% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 202 ms | 20% | not working last alive | |
| 999 | HTTP | 🇵🇪La Merced | Anonymous | – | 3524 ms | 19% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 2352 ms | 14% | not working last alive | |
| 999 | HTTP | 🇵🇪Cusco | Transparent | – | 3961 ms | 14% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 3701 ms | 13% | not working last alive | |
| 999 | HTTP | 🇵🇪Lima | Transparent | – | 3707 ms | 13% | 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 12 entries marked working. Mean recorded check success across these entries is 56%; mean recorded response time, where available, is 2796 ms. By protocol: HTTP (12). By anonymity level: Elite (1), Transparent (11). The most common ports are 999, 1083, 8080. Measurements come from recorded checks, not a promise of availability. Use ⟳ to recheck before use.
This slice groups public proxy records for Peru / HTTP. Use the recorded status and timestamps to interpret the table, then recheck before use. Availability and anonymity labels do not certify operator trust or privacy.
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.
People found this page by searching for
- HTTP
- proxy server HTTP
- free HTTP proxy
- free proxy list
- SOCKS5 & HTTP proxies
- socks5 proxy comparison
- public proxies
- dedicated ip
- working proxies
- what is a SOCKS5 proxy
- socks5 proxies
Real search phrases this page answers — the linked ones open the page that covers them in depth.