IP Lookup Shows the Wrong City? How to Check Your Proxy's Location
You set a session to Austin, ran a lookup through it, and the lookup says Dallas, or Round Rock, or just "Texas". Before you assume targeting failed, it helps to know what a lookup site is really telling you. Most of the time this is normal. Sometimes it is not, and the checks below separate the two in about ten minutes.
A lookup site gives an estimate from its own database, and databases disagree about residential IPs, especially at city level. A different country is a real problem. A different state is worth checking. A neighbouring town or the nearest big city is normal. What matters most is what the site you actually work with sees, not what a lookup site says.
Why a lookup can show a different city
There is no official register of where an IP address physically is. Every lookup service builds its own estimate from internet registry data, network routing and its own measurements, and then sells or publishes that. Three things follow from that:
- →Different services give different answers for the same IP. It is common for one to say Austin and another to say Round Rock or San Antonio.
- →A home internet connection is often placed at the internet provider's regional hub or the nearest large city rather than at the street it really sits on.
- →Databases are updated on their own schedule, so an answer can be out of date for an IP that moved recently.
Country is the most reliable level and city is the least. That is true of every proxy provider and every lookup service, which is why a nearby town in the reply does not mean the targeting failed.
Step 1: Confirm what you actually asked for
- 1In My Proxies, open the session and go to its Edit tab. Check that Country, State / region and City are what you expect. If City says Any, you have not asked for a city at all.
- 2Open the Credentials tab and read the Username. The location is spelled out at the end, for example -country-us-state-texas-city-austin. If there is no -city- part, the session is targeted at state or country level only.
- 3If you changed the location recently, copy the Username again. Changes apply to new connections only, so anything still running with the old username keeps its old behaviour until you swap the new one in.
The City list stays disabled until a state or region is chosen, and a city that is not in the list cannot be targeted. In that case choose the state or region instead.
Step 2: Test more than once, and check the lookup is seeing the proxy
One lookup tells you very little. Run the same test several times and look at the pattern. This sends five requests through a rotating session and prints the IP and the location each lookup reports. Replace YOUR_USERNAME and YOUR_PASSWORD with the values from the Credentials tab, and use the port shown there.
PROXY="http://YOUR_USERNAME:YOUR_PASSWORD@proxy.globproxy.com:9000"
for i in 1 2 3 4 5; do
curl -s -x "$PROXY" https://ipinfo.io/json | grep -E '"(ip|city|region|country)"'
echo "---"
done- →If the answer shows your own location or your own internet provider, the proxy is not being used. Check that the proxy setting applies to https addresses and that the username and port are copied in full.
- →A rotating session should show a different IP on most runs. If you see the same one every time, check that you are using the rotating port on the card. A very narrow target, such as a single city, also has fewer IPs to choose from.
- →On a sticky session the IP should stay the same until its lifetime ends. A sticky session holds one IP for a time you choose, from 1 minute to 24 hours.
Step 3: Read the result
| What the lookup says | What it usually means | What to do |
|---|---|---|
| Same city | Targeting and the database agree. | Nothing. |
| Neighbouring town or the nearest big city | Normal for residential IPs. Databases disagree at this level. | Cross-check with a second lookup, then judge by what your target site sees. |
| Same country, different state | Worth a second look. Test several IPs and a second lookup site. | Widen to state level if the city does not matter, or contact us with the details below if it persists. |
| A different country | Not expected. | Repeat the test, confirm the username from Step 1, then contact us. |
| Your own location | The proxy is not in use. | Fix the client setup, see Step 2. |
For the cross-check, use two or three different lookup services rather than one. If most agree on the area you asked for, the targeting is working even if one outlier disagrees.
What your target site sees is what counts
A lookup site is not the thing you care about. Google, an ad platform or a store each decide where a visitor is using their own data, and it can differ from every public lookup. If your goal is local search results or a city-specific price, test that directly: run the real task through the session and check that the results match the place you wanted. That is the test that matters, and it is the one to send us if something is wrong.
If you need a specific city to be right
- 1Make sure State and City are both set, not just the country.
- 2Use a sticky session so the IP stays put once you have checked it. On the Sticky sessions tab choose + new session, and create several at once (1, 5, 10 or 25). Each named session is its own fixed endpoint with its own IP.
- 3Look up each session's IP and keep the ones whose location matches what you need. Use remove on the rest to take them off your list. Remove only hides a session from the list; its IP keeps working until its lifetime ends.
- 4Create these fresh after changing a location, so you are sure you are testing the new setting.
A lookup request is tiny, so checking several IPs costs almost no bandwidth.
One city draws from a much smaller pool than a whole state, and one internet provider (ISP) from a smaller pool than a whole country. If a tightly targeted session is slow, repeats IPs or fails, widen it first: drop the city, then the state. An ISP is country-wide and is not combined with a state or city; if an ISP session fails with “no proxies available”, pick another ISP or use the country only. Many tasks that feel like they need an exact city work well at state level.
When to contact us, and what to send
Contact us if the country is wrong on repeated tests across more than one lookup site, if the state is consistently wrong, or if the session works but your real task still shows the wrong place. Open Support at the bottom of the dashboard sidebar and choose Report an issue. It helps a great deal if you include:
- →The session's label and the Username from the Credentials tab, with the password removed.
- →The targeting you chose on the Edit tab (country, then either a state and city or an ISP).
- →The date and time of the test, and your time zone.
- →The IPs you got and what each lookup service said, for at least three runs.
- →What your real task showed, if that is where you saw the problem.
Never send your password. The username and the IPs are enough for us to investigate.
Frequently asked
Still stuck?
Email us at support@globproxy.com and include your account email and what you see on screen.
Contact support →