About 12% of people who try to place a bet from a state where their sportsbook doesn't hold a license end up blocked by geolocation checks, according to operator-side data on cross-state attempts. That's not a rounding error — it's roughly one in eight would-be bettors hitting a wall that didn't exist a decade ago. And the wall is getting taller as more states come online with their own rules.

What "geo-fenced" actually means at the moment of a bet

Geolocation isn't a single check. A typical regulated book runs a chain: GPS on the phone, Wi-Fi network triangulation, IP address lookup, and sometimes a carrier-level signal. If any layer puts you outside the licensed state, the bet gets rejected — often with a generic "you appear to be outside your state" message that tells you nothing about which layer failed.

That vagueness is where a lot of the 12% comes from. People near a border, people on a work VPN, people whose home Wi-Fi router registers to an exchange point two towns over — they're physically legal, but the stack disagrees.

Where the blocks cluster

Border metros do most of the damage. Think Kansas City (Kansas and Missouri), the Quad Cities (Iowa and Illinois), Memphis (Tennessee and Mississippi), and the Philadelphia–Camden corridor. A bettor sitting in a legal state 400 feet from a bridge can trip a Wi-Fi or IP check that resolves to the illegal side.

Three patterns show up repeatedly in operator logs:

  • VPN users. Books generally ban VPNs outright, but plenty of casual users have one running from work or a privacy app and don't know it.
  • Shared networks. Apartment buildings, dorms, and hotels with a single public IP get flagged when that IP maps to a neighboring state.
  • Device permissions. A browser with location services off forces the book to fall back on weaker signals, which fail more often.

The compliance trade-off nobody advertises

Each state sets its own geolocation standard, and some are stricter than others. A book that accepts a looser signal in one state can't reuse that tolerance in another, so the same user experience varies by where you're standing. Operators would rather block a legal bettor than eat a fine — and the fines are real. Regulators have levied six-figure penalties for accepting wagers from out-of-state users, so the incentive runs one direction.

The cost lands on the customer: a rejected bet, a confusing error, and sometimes a support ticket that takes a day to resolve. For a $10 same-game parlay, most people just close the app.

What the 12% doesn't capture

The figure counts attempts that got blocked, not people who gave up before trying. Someone who knows their book won't work at their cousin's house in a non-legal state may never open the app at all, so the true friction number is probably higher. It also doesn't count the reverse case — bettors who successfully spoof location and get through, which is the compliance problem the whole system exists to prevent.

The open question

As more states legalize and the map fills in, does that 12% shrink on its own — or does it stay stubborn because the failures are geographic, not regulatory? Border towns don't move. Neither do shared Wi-Fi networks or the habit of leaving a VPN on. The interesting test is whether operators start publishing clearer error messages and letting users re-verify, or keep the vague rejection as the safe default. If you're the one getting blocked, the difference between "we can't verify your location" and "turn off your VPN" is the whole experience. And if you do get through, the usual rules still apply: set a deposit limit before the app decides for you.