USACHigh CostAnnual Requirements
Submit Data in the HUBB

Submit Data in the HUBB

The HUBB Portal

USAC closely monitors compliance with Connect America Fund (CAF) broadband build-out mandates to ensure that carriers receiving support are using it to expand high-speed Internet access to close the digital divide in rural America. Carriers participating in funds with fixed broadband deployment obligations must build and maintain networks that provide voice service and broadband at required speeds to a set number of locations in eligible areas over a defined timeline, with interim and final milestone deadlines. And they must report their progress in meeting their CAF deployment obligations by filing and certifying deployment data annually with the High Cost Universal Broadband (HUBB) portal showing where they are using funding to deliver service.

This information includes date of deployment and minimum upload and download speeds available for every location where they offer broadband supported by the program. Carriers must also report the address and latitude and longitude coordinates for every location served with CAF support, or report deployment using Location IDs from the Broadband Serviceable Location Fabric (Fabric). The Fabric, a single, standardized dataset of all locations in the U.S. where fixed broadband access is available or could be installed, serves as the foundation for FCC collection of fixed-broadband-availability data through the Broadband Data Collection and FCC mapping of fixed-broadband availability on the National Broadband Map. The FCC also relies on the Fabric to determine broadband deployment obligations for several newer CAF programs, and carriers in these programs report deployment data in the HUBB using Fabric Location IDs, which are the Location IDs from the Fabric that identify the locations where the carrier must offer service.

The HUBB conducts automated, real-time validation checks of the deployment data submitted by the carriers. The system validates, for instance, that a location’s latitude and longitude coordinates fall within an area eligible for funding, or that a reported Fabric Location ID is included on the list of locations where a carrier is required to deploy service. The HUBB also checks to be sure that the location is not a duplicate of one that has already been filed and that the date of deployment falls within the timeline of the fund in which the carrier participates. And it calculates carrier progress toward meeting a fund’s broadband build-out obligations, including interim and final deployment milestones. The HUBB will not accept locations that do not pass these automated validation checks and carriers will not receive credit for those deployments.

The HUBB dataset is the foundation for the Connect America Fund (CAF) Map and the Connect America Fund (CAF) State Map, interactive online maps that show the impact of CAF support on broadband expansion in rural America. The CAF Map displays the geographic areas that are eligible for CAF support, as well as the specific fixed locations where participating carriers report offering mass-market, high speed Internet service funded by the program. The CAF State Map provides a big-picture, state-level view of CAF-supported deployment. Note that the CAF Map and the CAF State Map only reflect deployment data reported by carriers using latitude and longitude coordinates, and do not include deployment reported by carriers using Fabric Location IDs.

In addition, the HUBB serves as a starting point for a more in-depth verification process  to confirm deployment to a random sample of locations reported in the system. All carriers participating in CAF programs with defined broadband build-out obligations are subject to this verification process, with verification reviews tied to annual deployment milestones, and should be prepared to submit documentation that serves as proof of deployment for each HUBB record selected for review. The HUBB is also a starting point for the  Performance Measures compliance framework, which requires carriers to conduct speed and latency testing of CAF-supported networks to ensure that broadband service subsidized by the Connect America Fund meets basic performance standards so that people living in rural communities have access to the same high-quality networks as those living in urban areas.

The HUBB is accessible through USAC’s E-File system. Please see USAC’s Multifactor Authentication Troubleshooting FAQs for help logging into E-File.

HUBB Filing Requirements by Fund

Carriers participating in the following funds have until March 2, 2026, to file and certify data for all locations deployed with CAF support in 2025 or certify that they have “no locations to upload”:

  • Connect America Fund Phase II Auction (CAF II Auction)
    • CAF II Auction carriers face a final milestone for deploying broadband with speeds, usage allowance and latency consistent with their winning auction bids, and must be fully built out to 100 percent of their obligated location counts by the end of 2025 (100 percent milestone).
  • Alternative Connect America Cost Model (Original ACAM)
    • Original ACAM carriers face a final milestone for deploying broadband at speeds of at least 10 megabits per second downstream and 1 megabit per second upstream (10/1 Mbps) and must be fully built out to 100 percent of their obligated 10/1 Mbps location counts by the end of 2025 (100 percent 10/1 Mbps milestone).
  • Revised Alternative Connect America Cost Model (Revised ACAM)
    • Like Original ACAM carriers, Revised ACAM carriers face a final milestone for deploying broadband at speeds of at least 10 megabits per second downstream and 1 megabit per second upstream (10/1 Mbps) and must be fully built out to 100 percent of their obligated 10/1 Mbps location counts by the end of 2025 (100 percent 10/1 Mbps milestone). In addition, Revised ACAM carriers face a milestone for deploying broadband at speeds of at least 25 megabits per second downstream and 3 megabit per second upstream (25/3 Mbps) and must be at least 80 percent of the way toward meeting their final 25/3 Mbps build-out obligations as of the end of 2025 (80 percent 25/3 Mbps milestone).
  • Alternative Connect America Cost Model II (ACAM II)
    • ACAM II carriers face a milestone for deploying broadband at speeds of at least 25 megabits per second downstream and 3 megabit per second upstream (25/3 Mbps) and must be at least 80 percent of the way toward meeting their final 25/3 Mbps build-out obligations as of the end of 2025 (80 percent 25/3 Mbps milestone). ACAM II carriers must also meet similar deployment obligations for eligible locations on Tribal lands.
  • Connect America Fund Broadband Loop Support (CAF BLS)
    • CAF BLS carriers are not required to file in the HUBB for 2025 since the FCC has deferred the start of the next five-year deployment obligation term for CAF BLS carriers until at least January 1, 2026. (See FCC 23-118 and DA 25-75). USAC and the FCC, however, encourage CAF BLS carriers to keep their deployment data in the HUBB up to date while the commission considers future CAF BLS deployment obligations, and remind these carriers that they must at least maintain their coverage footprint. (See DA 25-75)
  • Rural Digital Opportunity Fund (RDOF)
    • RDOF carriers must submit any locations deployed since July 1, 2019.
    • Starting in 2025, RDOF carriers must report deployment data in the HUBB using the Broadband Serviceable Location Fabric (Fabric), a single, standardized dataset of all locations in the U.S. where fixed broadband access service is available or could be installed. How it works: Each RDOF carrier has access to a required locations list – which contains the Location IDs from the Fabric that identify the locations where the carrier must offer service – and must report deployment in the HUBB using Fabric Location IDs. The HUBB will validate that the reported Fabric Location IDs are included in that carrier’s list of required locations. RDOF carriers no longer report broadband deployment data in the HUBB using geographic coordinates (latitude and longitude) and addresses, as they have in the past. (See FCC DA 25-361).
      • Interim required locations lists for RDOF carriers are available here.
      • RDOF carriers have until March 2, 2026, to submit deployment data using Fabric IDs to show where they built out broadband using CAF support in calendar year 2025 (or certify that they have “no locations to upload”), and to resubmit deployment data using Fabric Location IDs for locations already reported in the HUBB using latitude and longitude coordinates and addresses. All certified RDOF locations previously reported in the HUBB using latitude and longitude coordinates and addresses are no longer visible to carriers in the system. Carriers can still access past deployment data through the CAF Map. (Carriers can view and download RDOF locations certified in the HUBB as of March 7, 2025, reflecting deployment through Dec. 31, 2024, through the CAF Map dataset on the USAC Open Data platform.)
    • RDOF carriers authorized in 2021 face a 60 percent milestone for deploying broadband with speeds, usage allowance and latency consistent with their winning RDOF auction bids and must be at least 60 percent of the way toward meeting their final build-out obligations by the end of 2025. (60 percent milestone) RDOF carriers authorized in 2022 or 2023 face a 40 percent milestone for deploying broadband with speeds, usage allowance and latency consistent with their winning RDOF auction bids, and must be at least 40 percent of the way toward meeting their final build-out obligations by the end of 2025. (40 percent milestone)
      • Any RDOF carrier that believes it cannot meet its 40 percent deployment milestone must notify the FCC and provide an explanation for the shortfall within 10 business days of the milestone deadline – which is Jan. 15, 2026, for carriers authorized in 2022 or later. RDOF carriers that miss this milestone will be subject to quarterly reporting and possible recovery of support. In addition, any RDOF carrier that has deployed to fewer than 20 percent of its required locations by the 40 percent milestone deadline and has not notified the FCC by the following March 1 will be considered immediately in default of program requirements and subject to support recovery, with no grace period. RDOF carriers that default in some authorized areas but continue to receive support elsewhere in a state must comply with this notification requirement.
  • Rural Broadband Experiments (RBE)
    • RBE carriers face rolling deployment milestone deadlines based on when they began receiving funding.
  • Alaska Plan (other than carriers with individualized performance plans that only require them to maintain service at existing levels)
    • Alaska Plan carriers must also submit node and link data showing any new deployments or upgrades made to the middle-mile fiber and microwave nodes or networks needed to deliver broadband service in areas eligible for CAF support or certify “no nodes to upload.” (An Alaska Plan wireline carrier must certify middle-mile data on behalf of its wireless affiliate.)
    • Alaska Plan carriers with individualized performance plans requiring them only to maintain service at existing levels over the program’s 10-year support term do not have defined deployment obligations and therefore do not have to file in the HUBB (although they were subject to the five-year service milestone certification that applied to all Alaska Plan carriers as of the end of 2021). USAC encourages these carriers to certify annually that they did not deploy service to any new locations during the previous year. If these carriers do deploy new locations or upgrade service to existing locations at any speed, they should report those locations in the HUBB. An Alaska Plan carrier may become subject to defined deployment obligations due to changed circumstances (such as access to new middle-mile capacity) and may get credit for any locations certified before those revised obligations become effective.
  • Bringing Puerto Rico Together (Uniendo a Puerto Rico) Fund and the Connect the USVI Fund (PR/USVI) Stage 2 fixed support
    • Starting in 2025, PR/USVI carriers must report deployment data in the HUBB using the Broadband Serviceable Location Fabric (Fabric), a single, standardized dataset of all locations in the U.S. where fixed broadband access service is available or could be installed. How it works: Each PR/USVI carrier has access to a required locations list – which contains the Location IDs from the Fabric that identify the locations where the carrier must offer service – and must report deployment in the HUBB using Fabric Location IDs. The HUBB will validate that the reported Fabric Location IDs are included in that carrier’s list of required locations. PR/USVI carriers no longer report broadband deployment data in the HUBB using geographic coordinates (latitude and longitude) and addresses, as they have in the past. (See FCC DA 25-361).
      • Interim required locations lists for PR/USVI carriers are available here.
      • PR/USVI carriers have until March 2, 2026, to submit deployment data using Fabric IDs to show where they built out broadband using CAF support in calendar year 2025 (or certify that they have “no locations to upload”), and to resubmit deployment data using Fabric Location IDs for locations already reported in the HUBB using latitude and longitude coordinates and addresses. All certified PR/USVI locations previously reported in the HUBB using latitude and longitude coordinates and addresses are no longer visible to carriers in the system. Carriers can still access past deployment data through the CAF Map. (Carriers can view and download RDOF locations certified in the HUBB as of March 7, 2025, reflecting deployment through Dec. 31, 2024, through the CAF Map dataset on the USAC Open Data platform.
    • PR/USVI carriers must deploy broadband with speeds, usage allowance and latency consistent with their winning Stage 2 proposals, and must be at least 40 percent of the way toward meeting their final build-out obligations as of the end of 2024 (40 percent milestone).
  • Enhanced ACAM
    • Starting in 2024, Enhanced ACAM became the first CAF program to report deployment data in the HUBB using the Broadband Serviceable Location Fabric (Fabric) – a single, standardized dataset of all locations in the U.S. where fixed broadband access is available or could be installed. How it works: Each Enhanced ACAM carrier has access to a required locations list – which contains the Location IDs from the Fabric that identify the locations where the carrier must offer service – and must report deployment in the HUBB using Fabric Location IDs. The HUBB will validate that the reported Fabric Location IDs are included in that carrier’s list of required locations.
      • See this page for the current list of Enhanced ACAM interim eligible locations, as of August 2025, and this spreadsheet for the most current authorization report, Enhanced ACAM Authorization Report 1.2, dated June 2, 2025. The FCC will finalize the required locations lists for Enhanced ACAM carriers no later than December 31, 2025, and the HUBB will validate the HUBB filing due March 2, 2026, and all subsequent HUBB filings against each carrier’s final list of required locations from its final eligible locations file.
    • Enhanced ACAM carriers should not report any deployment data for their previous funds (Original or Revised ACAM, ACAM II or CAF BLS) in the HUBB, but do need to resubmit locations already deployed and reported in the HUBB under their previous funds if those locations appear on a carrier’s required locations list for Enhanced ACAM. USAC did not migrate any locations already in the HUBB reflecting deployment under previous funds for carriers that transitioned to Enhanced ACAM. Enhanced ACAM carriers should resubmit these locations to the HUBB using Fabric Location IDs and the original date of deployment. USAC has updated the HUBB to allow these carriers to report deployment dates before 2024.

Carriers with 2025 deployment milestones must complete additional milestone certifications as part of the annual HUBB filing – including separate milestone certifications for separate deployment obligations by speed tier – and may face verification reviews tied to those milestones. Carriers subject to defined deployment milestones must notify the FCC and USAC, and relevant state, U.S. Territory or Tribal governments if applicable, within 10 business days after the applicable deadline if they have failed to meet a milestone. (See 47 CFR Section 54.320(d)) Carriers that miss milestones face increased reporting obligations and potential loss of support.

In addition to certifying their location data, all carriers must also complete a separate annual certification in the HUBB between Jan. 1, 2026, and March 2, 2026, to confirm that their filing activity for 2025 is complete.

As part of this annual certification, carriers that did not deploy any locations in 2025 must still log into the HUBB and certify “no locations to upload” between Jan. 1, 2026,  and March 2, 2026. The “No locations to upload” certification functionality is only turned on in the HUBB between Jan. 1, 2026, and March 2, 2026. (Carriers that did deploy locations in 2025 can file and certify those locations throughout the year.)

Accurate geolocation data is the key to filing successfully by latitude and longitude in the HUBB. Please see the USAC Geolocations Methods Guide for an overview of different methods for collecting accurate latitude and longitude coordinates.

Ensuring Consistency with BDC and Fabric Data

The FCC Broadband Data Collection (BDC) is regularly updating the National Broadband Map to show where broadband service is available nationwide, location by location, as reported by Internet service providers. The BDC relies on the Broadband Serviceable Location Fabric (Fabric), a single, standardized dataset of all locations in the U.S. where fixed broadband access service is available or could be installed. The FCC has contracted with CostQuest Associates to create the Fabric.

HUBB reporting is not currently based on the Fabric for carriers participating in most CAF funds. But the FCC expects carriers to compare the broadband deployment data that they are certifying in the HUBB with the broadband availability data that they are submitting in the BDC and to take steps to ensure the data aligns where appropriate.

As part of the process of reviewing/verifying data reported to the HUBB, the FCC or USAC will cross check fixed broadband deployment data submitted to the HUBB and BDC databases, and will require carriers to explain and correct identified discrepancies between the datasets.

The FCC does not expect carriers, when reviewing location data across the HUBB, BDC and Fabric to ensure consistency, to replace information in the HUBB with information from the BDC or the Fabric. Rather, carriers should examine these datasets and address general mismatches.

For example, if a carrier has certified in the HUBB that it has deployed broadband to four locations on a street where the Fabric only shows three serviceable locations, the carrier should determine the actual number of serviceable locations on the street and either: (1) change the number of locations in the HUBB to three, by removing the extra location that is not there, if there are only three locations; or (2) file a challenge to the Fabric to add the missing location, so that the Fabric reflects four locations on the street, if there are four locations.

In some instances, the Fabric may include locations that are not actually broadband serviceable, such as a dilapidated structure or stack of haybales. If a carrier discovers misidentified locations in the Fabric, the carrier should file a challenge to have those locations removed from the Fabric and should not report those locations in HUBB. (Please see the FCC Guidance on Location Reporting for Carriers Receiving CAF Support (DA 16-1363) for examples of locations not eligible for CAF support.)

The FCC reminds carriers that the Fabric reflects each broadband serviceable location as a single point or record defined by a set of geographic coordinates (latitude and longitude) that fall within the footprint of a building or structure. Each record in the Fabric also contains other attributes, such as primary address, unit count and building type code. Apartment buildings appear as a single location with multiple units in the Fabric, and carriers should treat them as a single location with multiple units for BDC and HUBB reporting purposes.

Similarly, a single residential parcel with two separate single-family homes may appear as a single location in the Fabric. If a carrier reports the two separate single-family homes as unique deployments in the HUBB, but filed an unsuccessful challenge to add the second home as a separate location to the Fabric, the carrier can file a challenge to adjust the unit count associated with that location in the Fabric to reflect the two units being served on the parcel.

To facilitate the type of analysis described above, CostQuest, with approval from the FCC, modified the User Tier 2 User Class Statement (“UCS”) for the CostQuest Data License Agreement in September of 2023. These modifications expand the FCC programs for which the Data and Derivatives can be used. In addition to permitting use of the Fabric in meeting Broadband Data Act (“BDA”) obligations, such as the Broadband Data Collection, the modified license now allows Tier 2 licensees, such as broadband Internet access service providers, to submit Fabric-derived filings to the FCC (and/or any FCC-established entities, e.g., USAC) for Universal Service Fund reporting obligations.

How to File

The HUBB portal is accessible through USAC’s E-File system. Please see USAC’s Multifactor Authentication Troubleshooting FAQs for help logging into E-File. Users must have one of the following HUBB entitlements to access the system:

  • HUBB SPO (Service Provider Officer): allows the user to enter and certify data.
  • HUBB SPU (Service Provider User): allows the user to enter but not certify data (typically provided to users inside the carrier).
  • HUBB SPA (Service Provider Agent): allows the user to enter but not certify data (typically provided to agents outside the carrier).

The individual listed as the company officer on the carrier’s Form 498 can assign these entitlements. Company officers or general contacts with questions about logging into E-File or E-File passwords should contact customer operations via email or at (888) 641-8722. For E-File questions, customer service can only help the company officer or general contact listed on a carrier’s FCC Form 498. Others should direct E-File questions to the company officer or general contact who established the carrier’s authorized user entitlements. Please see USAC’s 498 ID webpage for help registering for a Form 498 ID, also called a Service Provider ID (SPIN).

Officers who encounter trouble adding system-specific entitlements to a user’s account should email hcquestions@usac.org with the following information: the carrier’s SPIN; the system (Form 481, HUBB, PMM) to be accessed; the email address the officer uses to log into E-File; and the email address and user role (SPO, SPU or SPA) of the person who needs the entitlement.

Late Filings

An eligible telecommunications carrier will see a reduction of at least seven days of support for a late HUBB certification. After the first seven days following the annual filing deadline, USAC will continue to reduce support on a day-by-day basis, plus an additional seven days, until the required certification is complete. A carrier would lose seven days of support for a certification that is four days late, for instance. And a carrier would lose 21 days of support for a certification that is 14 days late.

The FCC grants a one-time, four-day grace period for a late HUBB certification. This means that a carrier will see no reduction in support for a late certification submitted within four business days of the filing deadline if it is the first time that the certification is late.

This option to use the one-time grace period applies across a carrier’s holding company, affiliates and other operating companies. This means that if a carrier takes advantage of the four-day grace period, the grace period will not be available for a HUBB filing in subsequent years to its affiliates or other operating companies that serve different study areas but are owned by the same holding company.

See 47 C.F.R. § 54.316(c) and  FCC 23-87, para. 146.

In addition, if a carrier discovers individual locations deployed during the prior calendar year that it failed to submit and certify by the annual HUBB filing deadline, it should submit and certify those locations in the HUBB as soon as possible. New FCC rules (FCC 23-87, para. 152-161) allow carriers to submit and certify “late-reported locations” and to count those locations toward their deployment obligations, but these carriers may be subject to support reduction based on the number of locations reported late as a percent of total locations reported and the number of days after the filing deadline that they are submitted. The FCC grants carriers a one-time grace period to submit and certify late-reported without penalty. The FCC also does not reduce support for late-reported locations if a carrier has demonstrated compliance with its final deployment milestone.

Previous Trainings

Additional Resources

Non-Fabric Instructions and Templates

Fabric Instructions and Templates