The Short Answer
IP geolocation is very accurate at the country level (95-99%), reasonably accurate at the city level (55-80%), and never accurate at the street level (0%). It cannot pinpoint a specific building, home, or room.
When you use a tool like TraceThatIP's IP Lookup, the location shown is an approximation based on registration data and network topology, not GPS coordinates.
This article explains how geolocation databases work, what affects accuracy, and what the data actually means.
How IP Geolocation Works
IP geolocation databases map IP addresses to physical locations using several data sources:
1. Regional Internet Registry (RIR) records
When an ISP or organization obtains a block of IP addresses, they register it with a regional registry (ARIN, RIPE, APNIC, LACNIC, AFRINIC). This registration includes the organization's physical address.
IP Range: 203.0.113.0/24
Organization: Telstra Corporation
Country: Australia
State: Victoria
City: Melbourne
This is the baseline data. It tells you where the organization is headquartered, which may or may not be where the IP is actually used.
2. ISP and carrier data
GeoIP providers negotiate data-sharing agreements with ISPs. ISPs know which city each IP block serves, because their infrastructure is physical - a DSLAM (Digital Subscriber Line Access Multiplexer) in Sydney serves Sydney customers.
3. Active probing and latency analysis
GeoIP providers run network probes from known locations. By measuring the round-trip time from probes to target IPs, they can triangulate approximate positions:
Probe in Sydney: 8ms latency to target
Probe in Melbourne: 22ms latency to target
Probe in Brisbane: 15ms latency to target
Conclusion: Target is likely near Sydney
4. Wi-Fi and GPS correlation
Some databases correlate IP addresses with Wi-Fi access point locations and mobile device GPS data (anonymized and aggregated). This significantly improves city-level accuracy for consumer IPs.
5. User-submitted corrections
Major GeoIP providers accept corrections from ISPs and organizations. If a company relocates, they can update their IP location records.
Accuracy by Geographic Level
Country-level accuracy: 95-99%
Country detection is extremely reliable. The RIR registration data alone provides this, since IP blocks are allocated by country.
The remaining 1-5% errors come from:
- Satellite internet (IP registered in one country, user in another)
- VPN and proxy services
- IP address transfers between countries
- Mobile roaming
Region/State accuracy: 80-90%
State or region detection is generally good. ISPs operate regional infrastructure, and their IP allocations follow geographic boundaries.
Errors come from:
- ISPs that serve multiple states from one IP pool
- Corporate networks with centralized internet gateways
- Users near state borders
City-level accuracy: 55-80%
City detection is where accuracy drops significantly. The exact percentage depends on the provider and the country:
| Region | Typical City Accuracy |
|---|---|
| United States | 70-85% |
| Western Europe | 70-80% |
| Australia | 60-75% |
| Japan/Korea | 75-85% |
| Southeast Asia | 50-65% |
| Africa | 30-50% |
| Rural areas (global) | 30-50% |
City-level accuracy is highest in dense urban areas with well-documented ISP infrastructure and lowest in rural or developing regions.
Street-level accuracy: 0%
IP geolocation cannot determine a street address. Period.
The coordinates returned by GeoIP databases are typically the geographic center of a city or postal code area. If an IP is geolocated to "Sydney, Australia," the coordinates might point to the center of Sydney's CBD, not to any specific building.
{
"ip": "203.45.67.89",
"city": "Sydney",
"loc": "-33.8688,151.2093"
}
The coordinates -33.8688,151.2093 point to central Sydney. The actual user could be anywhere in the greater Sydney metropolitan area (12,368 square kilometers).
What Affects Accuracy
Factors that improve accuracy
- Fixed-line broadband - Physical infrastructure ties IPs to locations
- Urban areas - Dense ISP infrastructure = better mapping
- Countries with organized IP registries - Better data quality
- Major ISPs - Well-documented IP allocations
- Static IPs - Do not change, easier to map accurately
Factors that reduce accuracy
- VPN and proxy services - IP shows VPN server location, not user
- Mobile networks - Cell towers cover large areas, IPs are pooled
- CGNAT - Multiple users share one IP across a wide area
- Corporate networks - All traffic exits from HQ, even if users are elsewhere
- Satellite internet - IP might be registered in a different country entirely
- CDN and cloud providers - IPs registered to datacenter locations
- Rural areas - Sparse ISP infrastructure, less data available
- IP address transfers - Recently moved IPs may have stale location data
The VPN problem
VPN usage is the single biggest source of "wrong" IP locations. If someone in Tokyo uses a VPN server in London, their IP will geolocate to London. This is working as intended from the VPN's perspective, but it means the "true" location is hidden.
You can verify this yourself: connect to a VPN, then check What's My IP. The location shown will be the VPN server's location.
Major GeoIP Database Providers
Several companies maintain IP geolocation databases. Each has different data sources and accuracy levels:
| Provider | Free Tier | Accuracy Focus | Update Frequency |
|---|---|---|---|
| MaxMind GeoIP2 | GeoLite2 (free) | High accuracy, industry standard | Weekly |
| IPinfo.io | 50K requests/month | Business-focused, ASN data | Daily |
| IP2Location | LITE (free) | Comprehensive, many fields | Monthly |
| ipapi.co | 1K requests/day | Developer-friendly API | Daily |
| DB-IP | Free tier available | Good European coverage | Monthly |
TraceThatIP uses reliable geolocation data to provide accurate results. Try it by looking up any IP address.
Testing Accuracy: Real-World Examples
Test 1: Known datacenter IP
# Google Public DNS
IP: 8.8.8.8
Expected: Mountain View, California, USA
Result: Mountain View, California, USA ✅
Datacenter IPs are almost always accurate because they have fixed, well-documented locations.
Test 2: Home broadband IP
IP: [Home ISP IP]
Expected: Actual suburb
Result: Correct city, wrong suburb (10km off)
City is correct, but the specific suburb/neighborhood is often wrong. This is normal.
Test 3: Mobile network IP
IP: [Mobile carrier IP]
Expected: Current suburb
Result: Major city in the state (30km off)
Mobile IPs are pooled across large regions. The result points to the carrier's routing hub, which could be in a different city.
Test 4: VPN IP
IP: [VPN server IP]
Expected: User's actual location
Result: VPN server location (different country) ❌ (by design)
VPN IPs always geolocate to the VPN server's location. This is the intended behavior.
Common Misconceptions
"The map shows my exact house"
The map pin on a GeoIP lookup points to coordinates associated with your IP range, typically a city center or ISP hub. If it happens to be near your home, that is coincidence, not precision.
"GeoIP is more accurate than GPS"
GPS provides 3-5 meter accuracy. IP geolocation provides 5-50 kilometer accuracy at best. They are not comparable.
"Police use IP geolocation to find criminals"
Law enforcement does not rely on GeoIP databases. They issue legal subpoenas to ISPs, who look up the exact subscriber information for a given IP at a specific timestamp. This provides the billing address, which is far more accurate.
"My IP location changed but I didn't move"
ISPs regularly reassign IP blocks and update their routing. Your IP address might change, and the geolocation of your new IP might map to a different city. This does not mean anyone moved.
How to Improve Your Own IP Location
If your IP geolocates to the wrong location and you want to fix it:
- Contact MaxMind: Submit a correction at maxmind.com/en/geoip-location-correction
- Contact IP2Location: Submit at ip2location.com/feedback
- Contact your ISP: Ask them to update their WHOIS/RIR records
- Wait: Database providers regularly update their data
Implications for Businesses
Content delivery
CDNs use IP geolocation to route users to the nearest server. Inaccurate geolocation means suboptimal routing and slower load times.
Fraud detection
Payment processors use IP location as one fraud signal. If a credit card registered in Sydney processes a transaction from an IP in Romania, it triggers a review.
Compliance
GDPR, data sovereignty, and content licensing require knowing which country a user is in. Country-level accuracy (95-99%) is generally sufficient for compliance.
Advertising
Location-targeted ads use IP geolocation. City-level inaccuracy means some users see ads for the wrong city. Advertisers generally accept this as a limitation.
Summary
IP geolocation is a useful approximation, not a precision tool. It reliably identifies countries and usually identifies cities, but it cannot pinpoint specific locations. Understanding these limitations helps you use the data appropriately.
Test it yourself:
- Look up any IP address to see its geolocation data
- Check your own IP's location and see how accurate it is
- Learn what someone can do with your IP
- Understand public vs private IPs
