Skip to main content
SOCKS5 PROXY ENDPOINT NOT CURRENTLY VERIFIED

64.83.43.226:5555 SOCKS5 proxy

This endpoint previously passed our checks, but it does not have a currently eligible successful result. Use a fresh alternative below. Its source-reported location is Japan. Measurements are from local-a and can differ on your network.

Unverifiedcurrent publication status
—latest successful response unavailable in latest check
16 / 17successful / total attempts
Japansource-reported endpoint country

Endpoint facts and current evidence

Proxy address
64.83.43.226:5555
Connection protocol
SOCKS5
HTTPS capability
No currently eligible result
Endpoint location
Japan (source-reported)
Last observed exit IP
64.83.43.226 (successful check)
Latest attempt
2026-10-13 20:39:52 UTC
Last successful check
2026-10-13 20:22:44 UTC
First detailed observation
2026-10-13 16:11:42 UTC
Assigned checker
local-a
Observed success
94.1% across 17 attempts
Median successful response
2,009 ms across 16 retained successful checks
Discovery sources
proxyscrape, monosans
Publication expiry
Excluded from current downloads
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 64.83.43.226:5555

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.4,502 ms maximumOlder checksLatest checks16:11:42 UTC: 4502 ms16:27:58 UTC: 1909 ms16:44:55 UTC: 2063 ms17:02:02 UTC: 2434 ms17:19:41 UTC: 1928 ms17:35:48 UTC: 2014 ms17:52:37 UTC: 1916 ms18:08:16 UTC: 2086 ms18:25:30 UTC: 1949 ms18:41:31 UTC: 2005 ms18:58:35 UTC: 1949 ms19:15:32 UTC: 1942 ms19:32:43 UTC: 3462 ms19:50:13 UTC: 2012 ms20:06:29 UTC: 3434 ms20:22:44 UTC: 1919 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
Passed1,919 ms64.83.43.226
Passed3,434 ms64.83.43.226
Passed2,012 ms64.83.43.226
Passed3,462 ms64.83.43.226
Passed1,942 ms64.83.43.226
Passed1,949 ms64.83.43.226
Passed2,005 ms64.83.43.226
Passed1,949 ms64.83.43.226
Passed2,086 ms64.83.43.226
Passed1,916 ms64.83.43.226
Passed2,014 ms64.83.43.226
Passed1,928 ms64.83.43.226
Passed2,434 ms64.83.43.226
Passed2,063 ms64.83.43.226
Passed1,909 ms64.83.43.226
Passed4,502 ms64.83.43.226

How to interpret this endpoint’s results

The assigned checker recorded 16 successful attempts out of 17 total attempts, an observed success rate of 94.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.

How to test this SOCKS5 proxy

This endpoint has no currently eligible successful result, so its connection action is disabled. Choose a recently checked alternative instead of relying on an old address. The measurement history is retained to explain why a saved link no longer appears in downloads.

The socks5h:// scheme in curl delegates destination hostname resolution to the proxy. Other clients may resolve DNS locally unless configured otherwise. SOCKS5 alone does not encrypt your traffic or prove UDP support.

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

Is 64.83.43.226:5555 currently working?

There is no currently eligible successful result, so it is excluded from downloads. The latest attempt was 2026-10-13 20:39:52 UTC. Availability from your network and to other destinations can differ.

Does the Japan label prove the exit country?

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