Geo-blocking is compliance, not marketing
The first thing to understand about US sportsbook geo-blocking is that it is not a customer-acquisition decision dressed up as a restriction. It is a compliance requirement imposed by the gaming commissions in every state where the operators hold a licence. DraftKings, FanDuel and BetMGM block California because if they took bets from California while licensed in New Jersey, Nevada or any of the other regulated states, they would lose those licences, face seven-figure fines, and potentially face federal Wire Act exposure. The economic value of California traffic, even at full scale, does not justify those risks. The block is therefore both deliberate and total — not a gap in the system, but a feature of it.
I have seen variations of “why does the app keep rejecting me” from California bettors for as long as US sports betting has been a regulated product. The mechanics are worth walking through because they explain why workarounds do not work and why the block is more sophisticated than people assume. The operators are not blocking based on a bettor’s billing address or self-declared location. They are blocking based on physical presence verification at the moment of bet placement, and the technology has been refined over a decade of regulatory pressure to be close to airtight.
See also: UFC at California tribal casinos as a legal option.
How geolocation verification actually works
The verification stack used by the major US sportsbooks operates on multiple layers simultaneously. GeoComply is the dominant vendor in this space, providing both a browser plugin for desktop access and an SDK embedded in mobile apps. The plugin and SDK collect a basket of signals — Wi-Fi access point identifiers, cell tower triangulation data, GPS coordinates from the device, IP-based location estimates — and feed them into a model that produces a confidence score for the user’s physical presence in the licensed state.
The model is conservative. If any signal indicates the user might be outside the licensed state, the bet is rejected. If multiple signals agree on the user being inside the state, the bet proceeds. The threshold for confidence is set high enough that false positives — a legitimate New Jersey user being told they are in California — are exceedingly rare, and false negatives — a California user being approved — are functionally non-existent for typical consumer devices.
The verification fires not just at login but at the moment each bet is submitted. A bettor who logged in successfully in Nevada and then drove across the border to California while the session was still open will have their next bet rejected on submission. The session does not assume the location persists; it re-verifies on each action. That continuous verification is what makes the block resistant to most casual circumvention.
The vendor’s reach is industry-wide. Almost every regulated US sportsbook uses the same underlying technology, which means a workaround that defeats one platform’s check would defeat all of them — and the vendor monitors for new evasion patterns continuously. Workarounds that worked briefly in 2021 have been closed for years.
Why VPNs rarely help
The most common misconception I hear is that a VPN will solve the problem. It will not. VPNs change the user’s apparent IP address; they do nothing about the Wi-Fi access points the device can see, the cell towers nearby, or the GPS coordinates the operating system reports to the app. The verification stack treats IP location as one signal among many, and disagreement between IP-reported location and other signals is itself flagged as suspicious.
The detection logic looks something like this. The IP says New Jersey. The Wi-Fi access points the device sees include a network whose ID has been geolocated to a residential block in Los Angeles. The cell tower the phone is registered to is in San Diego County. The GPS, if accessible, reports coordinates inside California. Any of those signals disagreeing with the IP triggers a hold on the session and usually a request for additional verification. A VPN that masks IP without spoofing all the other signals — which a consumer-grade VPN cannot do — actively makes the bettor more visible as a circumvention attempt.
Worse, attempted circumvention is itself a flagged behaviour. A platform that detects a VPN attempt typically does not just reject the current bet — it freezes the account pending review, may close the account permanently, and may forfeit funds in the account depending on the operator’s terms of service. The act of trying to bypass geolocation is treated as evidence of intent to violate the licensing conditions, and the operator’s interest is in being seen by regulators to treat that intent seriously.
What happens when geo-blocking detects an issue
The sequence after a geo-failure varies by operator but follows a predictable pattern. First, the immediate bet is rejected with a generic error message — “we are unable to verify your location at this time” or similar. The user is asked to re-attempt the verification by walking around to refresh GPS data, restarting the app, or moving to a different network.
If a second verification fails, the account moves into a hold state. Login may still work, but bet placement is disabled pending manual review by the operator’s compliance team. The review process can take from hours to days. The user receives an email asking to confirm their location, sometimes accompanied by a request for documentation — driver’s licence, utility bill, recent travel records.
If the operator concludes the user was attempting to bet from outside the licensed state, the account is closed. Funds in the account are processed according to the operator’s terms, which usually means winnings from bets placed during the suspected violation period are voided and the original deposits returned. A user who deposited $200, won $1,500 in bets placed from California, and was caught at withdrawal would typically receive the $200 back and forfeit the $1,500 in winnings.
The closure is reported in the operator’s internal compliance records and may be shared with other operators through industry information-sharing agreements. A user closed at one major book for geo-evasion may find their accounts at competing books also flagged. The industry treats this as serious enough to coordinate.
Edge cases at state borders
The technology has to handle physical realities that do not respect clean state borders. A Lake Tahoe resident who lives on the Nevada side of the lake but uses a California-side Wi-Fi network at their office faces a borderline verification problem; the operator has to decide which signals to weight more heavily. The general rule is that the verification system errs toward rejection in borderline cases — better to lose a legitimate Nevada user’s bet than to accept a California user’s bet by mistake.
Cross-border travel creates similar issues. A regular Nevada resident visiting Los Angeles for a weekend cannot place bets through their Nevada-licensed account while in California; the app verifies presence at each bet submission and will reject from California regardless of where the account is registered. The reverse is also true — a California resident who travels to Nevada for a UFC weekend can legitimately bet while physically in Nevada, and the bets settle normally, but the moment they return to California the geo-block resumes.
Connectivity issues add a layer. Indoor venues with weak GPS signals — casinos, hotels, basement apartments — sometimes produce verification failures even for users who are unambiguously in the licensed state. The operators have built fallback verification using Wi-Fi triangulation specifically for these cases, but the experience is more friction-prone than a clean outdoor verification. For the legal framing around all this, the regulatory architecture is detailed in the broader analysis of how California’s 2026 sports betting law operates, which sets out what the geo-block is actually enforcing against.
See also: how to bet on ufc in california — geo restrictions.
Tribal property geo exceptions
The one location-based exception that does function in California is on tribal casino property. Some tribal casinos in the state operate on-property sports betting under tribal-state compacts, although the offering is currently limited compared to a fully regulated commercial market. The verification stack inside those properties is configured to recognise the property’s coordinates as a licensed zone, and bets placed by users physically on the property can proceed where bets placed off-property would be rejected.
The mechanics are similar to a Nevada casino’s verification system. The property uses Wi-Fi triangulation, GPS, and sometimes additional internal beaconing to confirm the user is physically inside the licensed zone. Once the user leaves the property — crosses the parking lot exit, walks to the road — the verification rolls back and the bets are no longer accepted. The geo-fence is precise enough to handle the boundary cleanly in most cases, though edge cases on property perimeters occasionally produce verification issues that staff handle individually.
