Challenging the FCC Broadband Maps

I’ve written many times about the absurdity of using the FCC mapping data for identifying areas with or without broadband. I’ve lately been looking at the FCC mapping data in West Virginia and New Mexico – two of the states with the worst broadband coverage in the country – and the FCC maps are atrocious. I see counties where the claimed broadband coverage in the FCC maps is wrong for more than half of the geographic area.

Unfortunately, the FCC is about to award $20.4 billion in RDOF grants later this year based solely on these dreadful maps. Luckily, there are other grant programs that allow grant applicants to challenge the FCC data. This includes the USDA ReConnect grants and many of the state grant programs.

One of the few ways to challenge the FCC maps is with speed tests. Anybody undertaking such a challenge needs to be aware that the incumbent telcos might challenge your speed test results, and unfortunately, some of their criticisms will be right. This means that anybody challenging the FCC maps has to take some steps to maximize the effectiveness of speed tests. Here are a few aspects of administering speed tests that should be considered.

  • A speed test needs to distinguish between cellular and landline connections. Rural folks with no broadband connection or those using cellular for home broadband are going to take the test with their cellphone. While such results are interesting, cellular speed tests can’t be mixed into a challenge of landline broadband coverage.
  • Everybody needs to use the identical speed test because each speed test measures speed using a different algorithm. Never use a speed test from the incumbents – it might be baked to show too good results.
  • A challenge can be most effective if it can get feedback from folks with no broadband available at their home. You need to somehow solicit and include results from folks that can’t take the speed tests.
  • You also should be aware a speed test sometimes doesn’t work for somebody with really slow broadband or high latency. We recently sat on the phone with somebody using satellite broadband and they couldn’t get the speed test to complete, even after many attempts.
  • The biggest challenge is in mapping the results. If you map the results so precisely that the results can be overlaid on individual homes on Google Earth, then you have provided an incumbent ISP the chance to challenge the test results. They can likely identify homes where they aren’t the ISP, or homes that have broadband that meets the FCC speed thresholds, meaning that slow speed test results might be due to poor WiFi or some other reason. Ultra-precise mapping might also violate the privacy of the people taking the speed test, This is an issue that many state speed test programs have wrestled with – some of them take such care to mask the precise location of the data that their final product can’t be used to challenge the FCC maps. For example, if speed test results are summarized by Census blocks then the results incorporate the same kinds of problems that are included in the FCC maps. Probably the best approach is to embed the final results in a pdf that is of low enough resolution to not identify individual homes.

There is one other way to map broadband coverage. An experienced field technician or engineer can drive around an area and can identify every broadband asset in the field. They can precisely identify where the cable TV networks end, down to the house. They can identify field DSLAMs that generate DSL signals out of rural cabinets – and they can often precisely identify the flavor of DSL and know the maximum speed capability of a given unit. They can identify the location and height of wireless transmitters and can map out the likely coverage areas. This kind of effort is most effective at identifying where there is no broadband, A good technician can make a decent map of the likely maximum broadband speeds available in a given area – something that is rarely achieved on most rural networks. This kind of challenge could be expensive and time-consuming, and I’ve never seen a challenge done this way. But I know engineers and technicians capable of making highly accurate maps.

Communities can tackle speed tests – they can get households to take the same speed test, such as the speed test from Ookla, and then match and map the results using GIS data. This can be a lot of work. Mapping can also be provided by many telecom engineering companies. One of the lowest-costs solutions is a speed test by Neo Partners that administers the speed test and overlays the speed test results automatically on Google maps.

Even if you aren’t challenging a grant, communities ought to consider speed tests to better understand the broadband in their community. As an example, I worked for a city where the speed tests showed that one neighborhood had far slower speeds than the rest of the city – something the city hadn’t known before the speed test. We’ve done speed tests that showed that the incumbent was delivering more than the advertised speed – again, something worth knowing.