A state just opened a website that quietly attacks the hardest problem in community broadband: not getting connected — knowing, precisely, where you already are.

What launched

VT Speed Check, from the Vermont Community Broadband Board, has three parts: a speed test (desktop app in partnership with Ookla), an anonymously aggregated map of results in hexagonal cells, and troubleshooting guidance that explains what a given result actually supports ("2 megabits per second can support email, but your video and downloads won't be great..."). It is explicitly a supplement to the FCC's National Broadband Map, and the state has been compiling the underlying data for a while: 1,454,850 tests from January 2023 through September 2026, a baseline VCBB Communications Director Herryn Herzog described as "the baseline for comparison with future test submissions."

The map it answers

The FCC's map is built predominantly on provider-reported coverage data. The Ground truth problems are not speculative: a GAO report found the patchwork multi-agency approach produces an FCC map with inaccuracies that "can steer taxpayer dollars away from communities that actually need them." When a community is deciding whether to build, and later deciding whether the new network kept its promises, the numbers on provider maps are the numbers written by the parties being measured. Vermont's answer to that is a second dataset where the measurement comes from the people being measured upon.

Vermont is not alone: ILSR's count of similar statewide programs covers nine others — Colorado, Minnesota, Washington, Hawaii, California, West Virginia, New York, Pennsylvania, and Maine. The pattern exists; the open question is who runs it and where the raw bytes live.

Why the baseline matters — and when

This is the part with a deadline attached. Vermont's buildout is mostly fiber being delivered by community utilities, and the state will soon be able to ask the question every municipal network vote should see answered with data: did the delivered network deliver? Lehi, Utah's city network published honest year-one take rates. Vermont will be able to publish honest before-and-after speed distributions — because the tests were collected before the buildouts. The sequence is the lesson: measure first, build second, publish the delta. A town that starts collecting tests only after completion has no baseline against which anybody will believe its improvement claims.

Two caveats before copying

The engine is Ookla's. The data sovereignty caveat this site exists to write, written against its own side's effort: VT Speed Check's speed test runs on proprietary commercial infrastructure. The aggregation is anonymized and the policy is the state's; the engine's bytes traverse somebody else's network. A community running this pattern entirely on free software is possible today — self-hosted measurement (LibreSpeed and similar) produces usable per-home numbers with the raw data kept on the community's own disks. The trade is real in the other direction too: Ookla compatibility buys comparability against the largest commercial test corpus on earth, and a self-hosted tool has no comparable universe. This is not a reason to reject Vermont's choice. It is a reason a community deciding between engines should make it on purpose.

Voluntary tests skew. The people quickest to complain about speeds test; the unconnected cannot test at all — the blind spot sits exactly where the need is highest. VCBB knows: the board is piloting device donations to restorative-justice centers to widen participation, and explicitly asks residents to test at different hours and days to expose the evening congestion a single test hides. A community copying this should budget for the outreach, not just the map.

For the audience this site is for: the ask of Vermonters is "test your speed, and test it often." The ask of community builders is the harder sentence — the state got to 1,454,850 tests by asking for years, not weeks. Start the count now; the number is only leverage when it has a before.