Residential proxy problems are different from datacenter proxy problems: because the exit point is a real home connection, variability is high, a node can drop off the network at any time, and the symptoms often point to more than one cause.
This guide offers a diagnostic flow that narrows the problem down layer by layer. For general proxy errors you can also look at our checklist article as well.
The Diagnostic Flow
Each branch leads to a different set of solutions. Working on the wrong layer is the most common reason for spending hours without solving the problem.
Layer 1 — I Cannot Connect at All
On systems that embed parameters in the username, the most common error is a mistyped separator or parameter name. A typo usually comes back as a 407.
Quick verification command:
The fourth step is very valuable: if you can connect with credentials that carry no parameters, the problem is in the parameter format, not in the credentials.
Layer 2 — The Target Is Blocking
If the connection is established but the target returns 403 or a CAPTCHA, the problem is not with how the proxy works but with how it is being used. Try the following in order:
Halve your request rate
This is the single most effective intervention. Most blocks stem from request intensity rather than IP quality.
Check consistency
Are the browser language, time zone and Accept-Language header consistent with the exit country? A mismatch is a strong signal.
Make session behavior more natural
Stop changing IP on every request; build a browsing pattern with short sticky sessions.
Review your header signature
A library's default header order is recognizable. Mimic the header set of a real browser.
Try a different country
Some targets are more tolerant of traffic from certain countries. The country where your audience is located usually gives the best result.
Layer 3 — Wrong Country / City
The location you requested is not coming through. Possible causes and checks:
- Parameter format: Is the country code two letters, lowercase? Follow your provider's documentation to the letter.
- Pool depth: There may be no node online in that region at that moment; the system may have fallen back to the country level.
- Database difference: The provider and the target may be using different geolocation databases.
- Cache: The target site may be storing your previous location in a cookie; start a clean session.
For a detailed method see our city targeting article, and to verify the exit location see My IP Address page.
Layer 4 — Session Instability
Prove the key's stability by logging it. Most “sticky is not working” complaints originate from the key being regenerated on every request.
Layer 5 — Performance Problems
You connect, you are not blocked, but the job moves very slowly. Things to check:
| Symptom | Possible cause | Solution |
|---|---|---|
| High and variable latency | The nature of a home connection | Filter out slow nodes with a health score |
| Frequent timeouts | The node is going offline | Increase the timeout, add a single retry |
| Concurrency bottleneck | The account limit is being exceeded | Pin the connection pool below the limit |
| Slowdown at night | Pool depth is dropping | Schedule heavy jobs for daytime |
| Drops on large files | Upload bandwidth limit | Chunked download or a different pool |
What to Send When Reporting to Your Provider
A good error report significantly shortens resolution time:
Never share your password. Sharing the parameters in your username, on the other hand, is necessary for diagnosis and poses no security risk.
Quick Checklist
- Is the quota used up? Check in the dashboard.
- Can you connect with the basic credentials without parameters?
- Does an exit IP come back, and is its country correct?
- Is the rate too high? Halve it and try again.
- Is the session key really constant? Log it.
- Are the language and time zone consistent with the exit country?
- Is the problem on one target or on all targets?
- Does a direct connection (without the proxy) work?
Summary
The key to solving residential proxy problems is placing the symptom in the right layer: connection, blocking, geolocation, session or performance. Each layer has its own diagnostic commands and solutions. The two most common root causes are the parameter syntax in the username and an excessively high request rate. To speed up your tests see proxy checker, My IP Address and ping test tools.