Sunday, February 25, 2024

AT&T’s two pronged fiber build out strategy

AT&T appears to be pursuing a two pronged strategy to build out fiber to the premises (FTTP) delivery infrastructure. The first is targeting densely built up metro areas with its Gigapower joint venture with BlackRock’s Global Infrastructure Fund. The second using subsidies extended to the states from the 2021 Infrastructure Investment and Jobs Act’s (IIJA) Broadband Equity, Access, and Deployment (BEAD) Program to build FTTP infrastructure in less densely developed areas that meet the program’s funding eligibility requirements.

Last fall, AT&T urged states to award the BEAD subsidies for contiguous builds that qualify as unserved (where at least 80 percent of serviceable addresses in the project are not offered throughput of 25/3 Mbps or better) and underserved (where at least 80 percent of serviceable addresses are not offered throughput of 100/20 Mbps or better). However, under BEAD, states must first exhaust their funding allocations on subsidies for projects addressing unserved locations.

As noted in the above linked blog post, AT&T’s BEAD funding appears predicated on the two generations of Digital Subscriber Line (DSL) technology that runs over its legacy copper voice telephone delivery infrastructure. The first, ADSL, will in many less densely developed areas qualify as unserved since it typically provides bandwidth lower than 25/3 Mbps. However, these areas are often adjacent to those served by its second generation VDSL technology. Those areas won’t qualify as unserved but could likely qualify as underserved.

Federal and state officials overseeing the award of BEAD funds will likely come under pressure from AT&T to liberally interpret the program rules to allow subsidization of contiguous FTTP projects spanning areas including both types of DSL technology. Expect AT&T to argue that this will provide the most efficient use of the funds and cover the greatest number of serviceable locations as well as meeting the BEAD program's preference for FTTP.

No comments: