As BEAD-funded broadband projects move from awards and planning into deployment across North Carolina, South Carolina, and Georgia, a separate and less visible set of obligations is coming into force alongside construction. Under performance measures finalized by the National Telecommunications and Information Administration in September 2025, BEAD subgrantees are required not only to build a network, but to demonstrate, on a recurring basis and for years afterward, that it performs to federal standards.
The Numbers Subgrantees Now Have to Hit
The rules are specific. A subgrantee’s speed test results have to show that at least 80 percent of download and upload measurements meet or exceed 80 percent of the committed tier — a project promising 100/20 Mbps service has to show most subscribers actually getting at least 80/16. Latency has to stay below 100 milliseconds on at least 95 percent of measurements, taken from a randomized sample of active subscribers and routed through FCC-designated exchange points rather than a subgrantee’s own internal servers. Testing is conducted during peak hours, 6 p.m. to midnight local time, over a one-week measurement period, and under the federal baseline it happens annually — not quarterly, as earlier drafts of the rule once considered. Networks are also expected to stay online, with total outages capped at roughly 48 hours a year outside of scheduled maintenance and federally recognized disasters, corresponding to about 99.45 percent annual uptime.
None of this is unusual by telecom industry standards. What’s newer is who now has to answer for it. A construction contract ends when the fiber is lit and accepted. These testing obligations run for the length of what NTIA calls the federal interest period — for terrestrial BEAD subgrants, this period extends 10 years after the year of subgrant closeout — and the entity bearing the reporting burden is often the local subgrantee itself: a municipality, a utility, or a smaller ISP that may not have built continuous network monitoring into its operations before.
The Administrative Weight Behind the Numbers
The technical thresholds are only part of what’s required. Results have to come from a verifiable random sample rather than hand-picked locations, each committed technology and speed tier has to be tested separately, and raw data has to be retained and certified by a corporate officer with supervisory and budgetary authority over network operations, not simply summarized in a report. States can require corrective measures, including more frequent testing, if a subgrantee is later found out of compliance, but they cannot loosen the underlying annual baseline or the speed and latency thresholds themselves.
For a subgrantee without dedicated network operations staff, meeting that bar on an ongoing basis is a different kind of project than the one that got the fiber built. It requires infrastructure most construction contracts don’t include: automated testing tools, IXP-routed traffic, data retention systems, and someone accountable for certifying results every year, indefinitely, for the life of the federal interest period.
Who Ends Up Owning This
That question is landing, in practice, on organizations that were never built to answer it. A small municipal utility or a rural ISP that competed successfully for BEAD construction dollars doesn’t automatically have the monitoring infrastructure, the reporting discipline, or the staff to sustain that compliance burden for a decade. This is where managed network operators are increasingly being brought in, not to build anything, but to carry the ongoing measurement and reporting obligations that construction contracts were never designed to cover.
One example of the kind of operator built around that gap is Anaptyx, a Myrtle Beach company that has been designing and running wireless networks since 2007. Its Beyond Wi-Fi platform segments administrative, public safety, and guest traffic on the same physical network and runs DNSFilter’s threat protection at the network level — infrastructure that predates the current BEAD rules but maps closely onto what continuous compliance now requires. Anaptyx’s COO, Kenneth Carnesi, Sr., has also written about the funding mechanics behind this obligation in Federal Broadband Funding – BEAD – Broadband Equity, Access & Deployment, a guide aimed at the small IT vendors and MSPs now navigating this exact requirement.
Construction completion dates get headlines. Performance measure compliance does not, largely because it isn’t a single event. It’s a recurring, annual obligation, and it does not end when construction wraps. For the municipalities, utilities, and smaller providers now finishing builds across the Southeast, meeting federal standards once is not the finish line — the reporting and performance requirements continue for as long as the federal interest period runs.
