AT&T said it is working with property owners, management groups and developers on deals that would clear the way for the telco to deploy its fiber-based “GigaPower” platform to apartments and other types of multiple-dwelling units (MDUs).
AT&T said the plan, which would expand the reach of its 1 Gbps-capable service, is to focus initially on areas where GigaPower is launched or will soon be launched: Atlanta; Chicago; Austin, Dallas, San Antonio, Fort Worth and Houston, Texas; Charlotte, Winston-Salem, Raleigh-Durham, and Greensboro, N.C.; Cupertino, Calif.; Jacksonville and Miami, Fla; Kansas City; Nashville, Tenn.; and St. Louis.
AT&T said its Connected Communities team is working with property owners and managers who are interested in bringing this service to their location, and has outlined three steps:
-Evaluation: Nominate property for GigaPower consideration at www.att.com/fiberproperties.
-Design: AT&T engineers will develop a fiber overbuild design of the legacy network to be approved by selected property stakeholders.
-Deploy: Once a deal is reached, AT&T will install the GigaPower network.
“We’re working with property owners, management groups, homeowner associations and developers to expand the availability of high-speed Internet over our AT&T GigaPower network,” Joni Arison, AT&T senior vice president of AT&T Emerging Markets, said in a statement. “This will make properties more attractive by offering Internet speeds up to 1 gigabit per second so residents can quickly connect to the cloud, telecommute more easily, video chat in real-time and stream the latest entertainment.”
“We’ve seen tremendous growth in apartments, condos and communities. There’s also more demand by residents to stay connected to the content that matters most,” added Scott DeGarmo, president and CEO of Broadband Communities.
The smarter way to stay on top of the multichannel video marketplace. Sign up below.
Thank you for signing up to Multichannel News. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.