Skip to main content
HTTP PROXY ENDPOINT WORKING BY SUCCESSFUL CHECK

3.219.86.40:3128 HTTP proxy

This endpoint passed two HTTPS requests with valid destination certificates and a changed exit IP. Its source-reported location is United States. Measurements are from local-b and can differ on your network.

Passedcurrent publication status
—latest successful response unavailable in latest check
22 / 23successful / total attempts
United Statessource-reported endpoint country

Endpoint facts and current evidence

Proxy address
3.219.86.40:3128
Connection protocol
HTTP
HTTPS capability
Passed both HTTPS probes
Endpoint location
United States (source-reported)
Last observed exit IP
54.198.195.106 (successful check)
Latest attempt
2026-10-27 16:14:40 UTC
Last successful check
2026-10-27 15:58:35 UTC
First detailed observation
2026-10-27 10:23:14 UTC
Assigned checker
local-b
Observed success
95.7% across 23 attempts
Median successful response
796 ms across 22 retained successful checks
Discovery sources
webunblocker, monosans, ercindedeoglu, proxmint, stormsia, yakumo
Publication expiry
2026-10-27 17:14:40 UTC unless a later check changes status
Authentication
Imported without username or password
UDP and sustained bandwidth
Not measured

A pass confirms connectivity from one assigned checker to two test destinations. It does not verify operator identity, ownership, logging policy, anonymity or safety. Country is the endpoint’s reported location, not a guarantee about where a destination locates its exit IP.

Recent check history for 3.219.86.40:3128

This page retains up to 24 individual attempts received after detailed history was enabled. The lifetime attempt counters can therefore exceed the number of rows below. A failed check means the complete verification did not pass; it does not identify a specific cause. Missing measurements are never displayed as zero latency.

Successful HTTPS response times, oldest to newest. Failed checks have no response-time point.936 ms maximumOlder checksLatest checks10:23:14 UTC: 762 ms10:40:24 UTC: 788 ms10:56:40 UTC: 817 ms11:12:11 UTC: 862 ms11:27:53 UTC: 893 ms11:43:44 UTC: 734 ms11:58:51 UTC: 704 ms12:14:30 UTC: 861 ms12:30:30 UTC: 761 ms12:45:55 UTC: 748 ms13:01:32 UTC: 841 ms13:17:05 UTC: 797 ms13:33:23 UTC: 795 ms13:49:08 UTC: 761 ms14:05:42 UTC: 801 ms14:21:29 UTC: 804 ms14:36:48 UTC: 910 ms14:53:44 UTC: 790 ms15:09:08 UTC: 936 ms15:25:47 UTC: 803 ms15:42:45 UTC: 756 ms15:58:35 UTC: 766 ms
Each point represents one successful HTTPS response measurement. Exact values and failed attempts appear below.
Attempt time (UTC)ResultHTTPS responseObserved exit IP
Did not passNot measuredNot confirmed
Passed766 ms54.198.195.106
Passed756 ms54.198.195.106
Passed803 ms54.198.195.106
Passed936 ms54.198.195.106
Passed790 ms54.198.195.106
Passed910 ms54.198.195.106
Passed804 ms54.198.195.106
Passed801 ms54.198.195.106
Passed761 ms54.198.195.106
Passed795 ms54.198.195.106
Passed797 ms54.198.195.106
Passed841 ms54.198.195.106
Passed748 ms54.198.195.106
Passed761 ms54.198.195.106
Passed861 ms54.198.195.106
Passed704 ms54.198.195.106
Passed734 ms54.198.195.106
Passed893 ms54.198.195.106
Passed862 ms54.198.195.106
Passed817 ms54.198.195.106
Passed788 ms54.198.195.106
Passed762 ms54.198.195.106

How to interpret this endpoint’s results

The assigned checker recorded 22 successful attempts out of 23 total attempts, an observed success rate of 95.7%. This sample reflects the checker’s schedule, destinations and network; it is not an uptime guarantee. Response time includes connection setup and a small HTTPS response. Read how checks work before comparing these values with speed or ping measurements from another tool.

Advertisement

How to test this HTTP proxy

Download and use the cURL configuration

The Download config (.conf) button saves this endpoint’s proxy setting and short connection timeouts. Run it with cURL and the HTTPS destination you want to test:

curl --config "publicvpnlist-http-3.219.86.40-3128.conf" https://api.ipify.org

The Download address (.txt) button saves one protocol://IP:port line for clients that accept a proxy address. Availability is checked against the latest published results when you download. Follow the download guide for file formats and freshness limits.

For an application that accepts a proxy URI, use http://3.219.86.40:3128. In a host-and-port dialog, enter 3.219.86.40 as the host and 3128 as the port. Select HTTP explicitly.

This curl example routes only the single request through the endpoint. Compare the response with your direct public IP and keep certificate verification enabled.

curl --proxy http://3.219.86.40:3128 --max-time 10 https://api.ipify.org

For HTTPS destinations, the client uses CONNECT through this HTTP proxy. The proxy URI remains http://; an https:// proxy URI describes TLS to the proxy itself and is a different feature.

Use the Firefox setup guide for a browser-only test. If a connection fails, check the protocol, port and latest check time before trying another endpoint. Never disable HTTPS certificate validation or provide personal account credentials to an unknown public proxy.

Recently checked alternatives

Prefer a fresh result matching your application’s protocol. The links below use the same country where available, then the same protocol.

All checked HTTP proxies · Proxy list for United States · All proxy countries

Proxy or VPN: choose the right connection

This endpoint is an application proxy. Read what a proxy does, compare Proxy vs VPN and review public proxy safety limits. For VPN profiles, use the separate OpenVPN server catalog or VPN and tunnel directory.

Source attribution and endpoint questions

This endpoint was discovered in Webunblocker / Socks5Proxies, monosans, Ercin Dedeoglu, Proxmint, stormsia, yakumo / elliottophellia proxylist. PublicVPNList’s measurements are produced separately from source claims. See the source policy and retained license notices.

Is 3.219.86.40:3128 currently working?

The endpoint has a recent successful verification in the current catalog. The latest attempt was 2026-10-27 16:14:40 UTC. Availability from your network and to other destinations can differ.

Does the United States label prove the exit country?

No. It is the source-reported location of the endpoint address. The last successful check observed exit IP 54.198.195.106. A destination service may locate that exit differently or apply its own restrictions.

Why is the proxy page still here after a failed check?

Saved links retain their last measurements and recent history. An endpoint without a fresh successful result is removed from the live list and sitemap, and its detail page is marked noindex until it passes again.

For connection problems, see proxy troubleshooting. If you operate this endpoint or want to report incorrect metadata, use Contacts and include only the public address, protocol and approximate check time.