In another victory for Google Fiber, Nashville’s Metro Council awarded final approval to a “One Touch Make Ready” rule that Google Fiber said was necessary for it to accelerate its deployment in the city.
Final approval came way Tuesday of a voice vote, according to The Tennessean, noting that Nashville Mayor Megan Barry is expected to sign the bill into law.
“One Touch Make Ready appears to be a common-sense way of speeding up the deployment of high-speed internet throughout Davidson County," Barry said in a statement, per the paper.
The final approval could set up a legal battle. Area incumbent AT&T has already threatened to file a lawsuit if the ordinance was given the green light and follow legal steps it has already taken in Louisville, Ky., after that city approved similar rules.
Both AT&T and Comcast were disappointed in the result in Nashville, with AT&T arguing to The Tennessean that there are better alternatives than the 'One-Touch' policy, while Comcast adding that it would weigh whether "further proceedings" were necessary.
In a blog posted earlier this month, Chris Levendos, director of national deployment and operations at Google Fiber, outlined the reasons behind Google Fiber’s “incredibly slow progress” there, claiming that that of the 88,000 poles required to attach Google Fiber for its rollout, more than 44,000 will require make ready work, but just 33 of them have been made ready.
Google Fiber issued this statement following Tuesday’s vote:
"It’s a great day for Nashville. Congratulations to Nashville Metro Council and residents on passing Council Member Davis’ One Touch Make Ready ordinance on its third and final reading. This will allow new entrants like Google Fiber to bring broadband to more Nashvillians efficiently, safely and quickly. We look forward to continuing our work with NES and the local community."
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.