KEY TAKEAWAYS
CONTENTS
What an IP Address Can and Cannot Tell an App
An IP address is the numeric label that identifies a device’s connection to the internet. Services can look the address up in a database that maps address ranges to places, and the result is often right about the country. For anything finer, such as which state or city a person is in, the answer is much less certain, which is the main reason gambling apps do not treat an IP address as proof of where a player is standing.
This matters to players in a practical way. A location check that fails near a state border or on a mobile connection is often a sign that the available signals were not precise enough, not a sign that anything is wrong with the player. Understanding what IP location can and cannot do explains why apps ask for other information, such as the phone’s own location services.
This article covers what research says about IP location accuracy, what published technical standards require of gambling geolocation systems, and how the pieces fit together. It stays at the level of how the technology works and describes only legitimate ways to resolve a failed check. No app, operator or geolocation provider is named.
How IP Geolocation Works
IP geolocation is a lookup. A database keeps a long list of address ranges and, for each, a guess at where those addresses are used. When an app or server sees an address, it finds the matching range and returns the stored location. The device is not asked anything, which is why researchers call this a client-independent method.
The alternative is client-dependent location, in which the device itself helps. A phone can estimate its position from GPS, nearby Wi-Fi networks and mobile network signals. A research paper on database accuracy describes client-dependent methods as typically accurate to within tens of meters, while client-independent IP lookups are typically accurate at city level at best.
The difference comes from where the information originates. An address range is assigned to an internet provider, which may use it across a wide area, and the database entry is an estimate rather than a measurement. A phone’s location services measure what is around the phone right now. The wider picture of the signals gambling apps combine is explained in how gambling apps check your location and why it fails.
Under the Hood: What the Research Finds
Several independent studies have measured how accurate IP location databases are. A 2017 evaluation of commercial databases in the journal Information Technology and Control found that most reached nearly 100% accuracy at the country level, with one database at around 80%. At the region level the best databases returned around half of estimates correctly, and at the city level the best returned about 30%. The best median error distance was 10 km, in a data set that included many small cities with a median population of 17,000.
An earlier ACM study, published in 2011, concluded that databases can claim country-level accuracy but certainly not city-level, and that entries with very fine granularity did not make accuracy better. A 2021 study that used GPS-located smartphone addresses found that databases are more accurate on fixed-line networks than on mobile networks, and that the median accuracy was better than 3 km in some contexts, although it called reliance on such databases in densely populated cities premature.
A 2026 preprint titled Lost in the Prefix, which has not yet been peer reviewed, tested four major providers against reference measurements and reported median errors of 179 to 207 km on mobile networks, compared with 3 to 16 km on fixed networks, and found that about 70% of mobile address prefixes span more than 100 km. Because it is a preprint, its figures are best read as supporting evidence rather than settled fact, but the direction agrees with the peer-reviewed work: mobile addresses are the hardest to place.
Regulators have written this into technical standards. Pennsylvania’s geolocation technical standards require the geolocation system to disregard IP location data for devices on mobile internet connections, to discount IP location data for all other connections so that it is not used as the primary source, and to use pinpoint-accurate location data sources instead. Colorado’s Industry Bulletin 3 likewise tells systems to disregard IP location data for devices using mobile internet connections.
Walkthrough: A Location Check on Two Connections
The following is a hypothetical, simplified example of a geolocation check in a generic app, here called App A, with invented figures. Actual systems differ by state and provider.
- The player opens App A and tries to place a bet. The app asks its geolocation service to run a check.
- The service gathers signals from the device. On a phone with location services on, it receives position data from GPS, Wi-Fi and mobile signals, along with an estimate of how accurate that position is.
- The service looks at the IP address. The lookup returns a stored location for the address. For a phone on mobile data, the standards above tell the system to disregard this result.
- The service compares the position with the state boundary. It overlays the position, and the accuracy radius around it, on a map of the permitted area.
- The result is returned. If the whole accuracy radius is inside the boundary, the bet can go ahead. If the radius touches the boundary or crosses it, the check may fail even though the player is in fact inside the state.
- The player takes a legitimate fix. Turning on precise location, connecting to Wi-Fi or moving away from the border can improve the signals, after which a new check can be run.
Variations: Connection Type and How IP Data Is Used
How useful an IP address is depends on the kind of connection. The table summarises what the research and standards above say; the figures are drawn from the studies cited and can differ between databases and countries.
| Connection | What the research and standards say about IP location |
|---|---|
| Fixed-line (home or office) | More accurate than mobile; still not treated as a primary source by Pennsylvania’s standards |
| Mobile data | Least accurate in studies; standards in Pennsylvania and Colorado say to disregard IP location data |
| Country-level question | Databases are generally reliable, with most near 100% in one study |
| City-level question | Best databases about 30% correct in one study; best median error was 10 km |
If IP data is weak on accuracy, it still has a role. Standards in Colorado and North Carolina describe it as a trigger: a location check must run when the IP address changes during a session. A change of address is a cue to check again, not a measurement of position. Re-checks also run on a timer. Pennsylvania’s standard sets re-checks at 20 minutes for static or mobile connections, shortened to 5 minutes within 1 mile of the state border, and for mobile connections it bases the interval on distance from the boundary using an assumed speed of 65 miles per hour.
Myths and Limits
Myth: an IP address shows exactly where a person is. It does not. Research finds good country-level accuracy but much weaker region and city accuracy, and database entries are estimates.
Myth: a failed check means the app suspects the player. Most failures are signal problems, such as location services being off or an accuracy radius that touches a border. They are usually fixed by improving the signals.
Myth: more accurate IP databases solve the problem. The 2021 study found that paid versions are often not significantly more accurate than free ones, and the underlying limit is how address ranges are used, not the vendor.
A real limit: the studies measure general IP databases, not any particular gambling geolocation service, and results vary by country, network and year. This article reports what the sources say as of 2026 and cannot say how accurate any specific app’s check is.
Key Facts and What a Player Can Do
| Question | Short answer |
|---|---|
| Is IP location reliable by country? | Generally yes, in published studies |
| By city? | No; the best databases were about 30% correct in one study |
| Which connection is hardest to locate? | Mobile data |
| Do standards rely on IP location? | Pennsylvania and Colorado say to disregard it on mobile and, in Pennsylvania, not to use it as the primary source otherwise |
| What can a player do if a check fails? | Turn on precise location, connect to Wi-Fi, update the app, or contact support |
A player whose check fails can take only legitimate steps: make sure the phone’s location services are on and set to precise, connect to a Wi-Fi network if one is available, update the app, move away from a state border and try again, or contact the operator’s support. Re-checking after improving the signal is expected, since standards require apps to run the check again before allowing a wager when the first one fails.
Related Concepts and Next Step
For the full set of signals behind a check, start with how gambling apps check your location and why it fails. The difference that a phone’s precise location setting makes is explained in precise vs approximate location in gambling apps. Age checks use a different kind of signal, covered in how facial age estimation works, and the account system that ties checks to a player is described in what a player account management system is. Together they show how a platform builds confidence from several imperfect signals instead of trusting any one.
Frequently Asked Questions
Sources & References
- Komosný, Voznák and Rehman — Location Accuracy of Commercial IP Address Geolocation Databases, Information Technology and Control (2017)
- Poese, Uhlig, Kaafar, Donnet and Gueye — IP geolocation databases: unreliable? ACM (2011)
- Saxon and Feamster — GPS-Based Geolocation of Consumer IP Addresses (2021 paper)
- Lost in the Prefix: Revisiting IP Geolocation Accuracy Across Networks and Geographies (arXiv preprint, 2026; not peer reviewed)
- Pennsylvania Gaming Control Board — Technical Standards, Chapter 809b, Geolocation
- Colorado Division of Gaming — Sports Betting Industry Bulletin 3, Rule 7.10 Geofence Requirement
- North Carolina Administrative Code — 24 NCAC 06B .0405, Geolocation requirements



