Lesson — Coverage Maps Have Overstated Service

What is it?

This lesson captures a recurring failure: US broadband coverage maps, long built from provider-reported data at the census-block level, systematically overstated how many locations actually had service. If one home in a block could get service, the entire block was often counted as served.

Why does it matter?

Overstated coverage caused real communities to be labeled “served” and excluded from funding, so the measurement error directly denied investment to places that needed it, in rural Washington and nationwide.

How does it work?

Aggregating self-reported availability to coarse geographies, without independent verification, biases counts upward. The FCC’s newer location-level map and formal challenge process were created specifically to correct this, and challenges have moved the numbers.

Who benefits?

Communities and advocates who use the challenge process to correct their status and unlock funding, and programs that allocate money on more accurate data.

Who may be disadvantaged?

Areas that lack the capacity to file challenges may remain miscounted, and any residual optimism in the data still risks bypassing the hardest-to-serve locations.

What evidence exists?

The Government Accountability Office and independent researchers documented the overstatement for years, and FCC map revisions after the switch to location-level data and challenges confirmed material corrections.

What tradeoffs exist?

More accurate, location-level mapping with challenges is far better but slower and more expensive to maintain than simple provider self-reports.

Common misconceptions

A newer, better map is not perfect — improved methods reduce but do not eliminate overstatement, so a “served” label still warrants local verification.

What you can do next

Treat the broadband coverage-gap metric with this caveat in mind, and support local challenges to correct the record, via the linked node.