Skip to main content
SOCKS4 PROXY ENDPOINT RECENT CHECK PASSED

116.101.14.169:1090 SOCKS4 proxy

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

Passedcurrent publication status
1,834 mslatest successful response
4 / 7successful / total attempts
Vietnamsource-reported endpoint country

Endpoint facts and current evidence

Proxy address
116.101.14.169:1090
Connection protocol
SOCKS4
HTTPS capability
Passed both HTTPS probes
Endpoint location
Vietnam (source-reported)
Last observed exit IP
58.187.26.252 (successful check)
Latest attempt
2026-10-13 18:22:46 UTC
Last successful check
2026-10-13 18:22:46 UTC
First detailed observation
2026-10-13 12:46:20 UTC
Assigned checker
local-a
Observed success
57.1% across 7 attempts
Median successful response
1,889 ms across 4 retained successful checks
Discovery sources
monosans
Publication expiry
2026-10-13 19:22:46 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 116.101.14.169:1090

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.2,506 ms maximumOlder checksLatest checks17:33:34 UTC: 1882 ms17:49:48 UTC: 2506 ms18:05:39 UTC: 1895 ms18:22:46 UTC: 1834 ms
Each point represents one successful HTTPS response measurement. Exact values and failed attempts appear below.
Attempt time (UTC)ResultHTTPS responseObserved exit IP
Passed1,834 ms58.187.26.252
Passed1,895 ms58.187.44.85
Passed2,506 ms58.187.26.252
Passed1,882 ms58.187.26.252
Did not passNot measuredNot confirmed
Did not passNot measuredNot confirmed

How to interpret this endpoint’s results

The assigned checker recorded 4 successful attempts out of 7 total attempts, an observed success rate of 57.1%. 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 SOCKS4 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-socks4-116.101.14.169-1090.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 socks4://116.101.14.169:1090. In a host-and-port dialog, enter 116.101.14.169 as the host and 1090 as the port. Select SOCKS4 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 socks4a://116.101.14.169:1090 --max-time 10 https://api.ipify.org

The socks4a:// scheme asks the proxy to resolve the destination hostname. Older SOCKS4 clients may behave differently. The published check covers IPv4 TCP traffic, not UDP or a full-device VPN.

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 SOCKS4 proxies · Proxy list for Vietnam · 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 monosans. PublicVPNList’s measurements are produced separately from source claims. See the source policy and retained license notices.

Is 116.101.14.169:1090 currently working?

The endpoint has a recent successful verification in the current catalog. The latest attempt was 2026-10-13 18:22:46 UTC. Availability from your network and to other destinations can differ.

Does the Vietnam label prove the exit country?

No. It is the source-reported location of the endpoint address. The last successful check observed exit IP 58.187.26.252. 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.