Connection refused or timeout
First verify that the internet works without the proxy. Then check the port and protocol against the catalog row. An HTTP proxy entered as SOCKS5 will usually fail even if the endpoint is online. Prefer a result checked within the last few minutes and use a short timeout.
A timeout can also reflect network filtering or a destination the proxy cannot reach. Our tests use two fixed HTTPS endpoints; a pass does not promise reachability to every website. Switch to a different recently checked proxy before changing your operating-system settings.
The public IP has not changed
Check whether the application actually uses the proxy. Review browser bypass exceptions, client environment variables and per-request settings. Other applications are not automatically covered by a browser proxy configuration.
Use an explicit proxy option for a single request and compare the response to a direct baseline. A page showing a cached value can mislead, so reload or use a second IP endpoint. If the exit still matches the baseline, do not treat the request as verified through the proxy.
Certificate errors or unexpected login prompts
Stop using an endpoint that produces a certificate warning for a normally valid HTTPS website. Check your computer’s clock and try the site directly. Do not disable TLS verification, import an unknown root certificate or submit account credentials to make a free proxy work.
This catalog imports endpoints without usernames and passwords. An authentication prompt may mean the endpoint policy changed or the proxy type is wrong. Choose another endpoint rather than guessing credentials.
Slow responses and unexpected country
Latency in the table is measured from the assigned checker during a short HTTPS request. Distance, network congestion and endpoint load can make your result different. It is not a sustained speed benchmark.
Source-reported country refers to an endpoint IP database, not a promise about where a destination will locate your exit. Compare the exit address yourself and check multiple endpoints. For repeated work, prefer a trusted service with an explicit reliability agreement.
Useful details for a report
When reporting a catalog problem through Contacts, include the public endpoint, protocol, approximate check time and a short description such as “timeout” or “wrong country.” Do not include passwords, cookies, access tokens or private browsing history.
Read how checks work for publication and expiry rules, or return to the current proxy list to choose another endpoint.