CenturyLink says the FCC's new business data services (BDS) proposal could mean crippling rate cuts while ignoring evidence of competition.
The company accused the FCC of a flawed and dangerous approach that lacked transparency.
The FCC Oct. 27 scheduled a vote for the Nov. 17 public meeting on chairman Tom Wheeler's BDS revamp.
The chairman is proposing what is billed as a tech-neutral approach to regulating business broadband—credit card transactions and ATM connections, for example—regulating it wherever the FCC finds markets are not competitive, maintaining price caps on incumbent/independent local exchange carriers (ILECs) and regulating new competitive local exchange carriers (CLECS), including cable broadband providers on a case-by-case basis. Initially the proposal was to impose ex ante (before the fact) price regulation on incumbents according to a geographic approach, but that was changed to the case-by-case model.
On Friday, CenturyLink—which was no fan of the initial proposal—slammed the latest proposal and its ILEC price caps, saying there was no basis for cuts in ILEC rates and that the FCC was lowballing the cuts it was proposing.
The FCC based its new approach to business broadband (formerly called "special access") on several years of data-collection, but CenturyLink says the commission's new proposal "suggests an intent to ignore" evidence of competition and impose not only a phased-in rate reduction but in some cases an additional, initial, rate reduction.
"The layering of these reductions on top of one another is buried within the proposal, and has the potential to seriously damage providers’ ability to recover from lost income," the company told the FCC. "This drastic rate cut would cripple many providers’ ability to continue providing quality service, much less have money left to invest in broadband innovation for the future."
The smarter way to stay on top of broadcasting and cable industry. Sign up below.
Thank you for signing up to Broadcasting & Cable. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.