There is a lot of talk about improving the FCC broadband maps. I published a blog a few weeks ago that described a bill passed by the Senate that would require a new review of the FCC broadband maps. The bill is labeled the Modernization, Accountability, and Planning (MAP) for Broadband Funding Act.
I’m all for changes that would create an accurate broadband map. But I’m fairly certain that the FCC is not going to consider making the changes that would actually improve the maps. The biggest problem with the current maps is that speeds claimed by ISPs are sometimes far different than what is being delivered. Fixing that would require the FCC to actually look at what’s in the maps and challenge ISPs that exaggerate speeds. I can’t imagine the agency adopting new rules that would saddle itself with that responsibility.
There is an existing tool that could be used to compare claimed speeds to actual speeds. Ookla records millions of speed tests across the country for all ISPs. The FCC could buy the Ookla speed test records to compare against ISP claims. With AI and other new analytic tools, it wouldn’t be hard to compare Ookla speeds to FCC claimed speeds.
If speed tests were considered, ISPs would instantly yell that speed tests aren’t accurate enough to use to judge them. In many ways, they would be right. People often take speed tests when their broadband isn’t performing right. There are lots of homes where speeds are slower due to WiFi issues. A computer sitting close to the WiFi router will show faster speeds than a computer at the other end of a home. Many customers subscribe to lower speed tiers, which, by definition, don’t show the capability of the ISP.
But when large numbers of speed tests are used correctly, they are a valuable tool for understanding an ISP’s real performance. I’ve been lucky enough to work with counties that have purchased the full Ookla speed data set. Those tests provided them with enough data to do meaningful comparisons.
One of the things I learned in working with speed test datasets is that you must concentrate on the fastest speeds rather than average speeds. Doing so eliminates most of the concerns I discussed above. If an ISP claims data speeds of 100/20 Mbps to the FCC, but there are no speed tests over the course of a year that hit that speed, the ISP is exaggerating speeds. This kind of analysis can be used to ferret out exaggerated speed claims. This also worked in both directions – I’ve often seen faster speeds than the speeds claimed to the FCC, which means the ISP is underreporting speeds.
Speed tests can also be used to test broadband coverage claims. I was working with one county where a WISP was claiming coverage over more than half of the geography of the county. The Ookla speed test data for that ISP showed only a single speed test over the course of a year. It was clear that the WISP’s coverage claims were aspirational, not actual, and the County was able to use the Ookla results to challenge the broadband maps in the first BEAD map challenge. Without the Ookla tests, the County could not have made a map challenge, because the NTIA challenge rules wanted the County to find customers using the ISP in question and convince them to take speed tests. It’s obviously impossible to test an ISP that is not actually present.
Speed tests show all sorts of other interesting facts about ISP coverage. I’ve written several times in the past about how the speed for FWA cellular wireless quickly diminishes with distance from the tower. An FWA carrier might be delivering 300 Mbps to a customer within a short distance of a tower, but after a mile, speed drops to 100 Mbps. By two miles speed drops to 50-75 Mbps, and at three miles drop to the range of 25 Mbps. Most FWA speed claims in the FCC map will show 100 Mbps across the entire area around a tower, and much of that speed claim is overstated.
The FCC already spends a lot of money annually trying to get the mapping fabric right. But it’s pretty clear that the FCC doesn’t look at the speed data claimed by ISPs. The only time the FCC uses this data is when it published its annual report to Congress about the state of broadband. The FCC benefits by overstated maps since they tell a better story than what’s really available in rural America. If the FCC really wants to get serious about broadband mapping, why not buy the Ookla data twice per year to compare to claimed speeds?








