Common issues
Diagnostic flows for proxy down, wrong country IP, slow speeds, fraud score issues, suddenly broken proxies
If you have a specific error code, see Error codes. This page is for "something's wrong" diagnostics.
Is the proxy down?
Check status.eclipseproxy.com first. Real-time incident updates live there.
Status is green but proxy not working
- Proxy password reset? Old credentials return 407. Update all scripts.
- Wrong protocol/port? HTTP creds on SOCKS (or vice versa). Re-generate.
- Out of bandwidth? Check dashboard and top up.
- Target blocking? Test against
api.ipify.org. If works, target is blocking that IP type.
Wrong country IP
- Username typo? Re-generate from dashboard.
- No inventory? Try
-strict-offfor fallback. - Target geolocates differently? Verify with
curl -x ... https://ipinfo.io. If that shows right country but target disagrees, it's target-side detection.
Slow proxies
Measure with: curl -x http://USER:PASS@HOST:PORT -o /dev/null -s -w "%{time_total}\n" https://api.ipify.org (not ping).
Common causes: some regions slower, target is slow, bandwidth exhausted, wrong product for use case.
Worked yesterday, broken today
- Check status page.
- Reset password or change tools?
- Test against
api.ipify.orgto isolate. - Try different country or product.
High fraud score / IP marked as VPN
Datacenter IPs expected to have high scores. For Residential/ISP, contact support with screenshot (IPQualityScore, Scamalytics) for replacement.
Proxy works in cURL but not in my tool
Check: wrong protocol, system-wide proxy interfering, WebRTC leak, or tool reusing connection. Use fresh session ID per request.
What to include when contacting support
- Exact error message
- Proxy string (mask the password)
- Target URL (if shareable)
- What you've already tried from this page
Cuts ticket resolution time in half.