What the Map Says an Address Has, and How to Dispute It

How the Map Is Built

The FCC's national broadband map, relaunched in November 2022 under the Broadband Data Collection programme, replaced the long-criticised Form 477 system that had counted entire census blocks as served if a single household in the block could theoretically receive service. The new map works at the fabric level: every address and location unit in the country has its own record, drawn from the FCC's Location Fabric — a database constructed from tax records, building permits, satellite imagery and postal data.

Against that fabric, internet service providers submit availability filings twice a year. Each filing declares, address by address, what technology a provider offers and at what maximum advertised speed. The FCC does not independently verify those claims before publishing them. A provider that files a record saying it can deliver 100 Mbps downstream to a given address is taken at its word until someone objects.

Feasibility studies are public records, and most of them cite the same handful of towns.

Photo: Artem Podrez / Pexels

That self-reporting structure is where the map's well-documented weaknesses live. The Institute for Local Self-Reliance has catalogued cases in which providers reported service to addresses that had never seen a truck, a conduit or a working modem. Rural communities and tribal lands have found their locations marked served at speeds they have never received, making them ineligible for construction funding before a shovel could be discussed.

What the Challenge Process Allows

The FCC's Broadband Data Collection challenge portal allows four categories of challenger: individuals, local governments, other providers, and Tribal governments. Each can dispute a provider's availability claim on a specific location, either by asserting that the provider's advertised service is not actually available there, or by submitting evidence that the speeds claimed are not delivered in practice.

The edge of a service territory. Past it, a map dispute decides on paper who counts as served.

Photo: Adi Nagesh / Pexels

An individual challenger submits contact information and a brief description of the discrepancy — typically that they requested service and were told it was unavailable, or that a service address has been vacant land for years. Local governments can file in bulk, aggregating challenges across hundreds or thousands of addresses in a single submission. That bulk-challenge pathway has been heavily used by counties and municipalities trying to unlock BEAD eligibility for areas their providers had claimed were already served.

Once a challenge is filed, the provider has an opportunity to respond. If the provider fails to respond or cannot substantiate its original claim, the FCC updates the map record. A sustained challenge can reclassify a location from served to unserved or underserved, making it eligible for BEAD construction funding it would otherwise have missed.

The stakes are direct. NTIA's formula allocation — the method that divided $42.45 billion among states — was calculated from unserved location counts in the FCC map as it stood at a fixed date. States whose maps contained inflated provider claims received less funding than their actual connectivity gaps warranted. Correcting those records through challenges does not retroactively change a state's initial BEAD allocation, but it shapes which specific locations within a state can be targeted for construction projects.

What the Map Does Not Resolve

Availability and adoption are different things, and the map measures neither well. A location marked served at 100/20 Mbps may have a household that cannot afford the subscription, uses a device too old to use it, or has never been contacted by the provider in question. The map's fabric also changes: new construction, address corrections and provider updates mean that what the map says about a given address today may differ from what it said when a state's BEAD plan was submitted.

Local governments tracking BEAD eligibility for their jurisdictions — including places like Skokie that have invested in their own fibre infrastructure — have reason to audit the map regularly, file challenges where the record is wrong, and document those challenges in the public record. The challenge process is slow and adversarial by design; used rigorously, it is also the only official mechanism a community has to correct what the federal government believes it already has.