Summary

  • On 15 October 2026, FCC amendments to 47 CFR §§51.329 and 51.333 take effect after OMB approved the related information collections. Incumbent LECs may give required public notice through publicly accessible industry forums, industry publications or their websites; they no longer file the covered notices with the FCC for agency publication.
  • The FCC also removes the Part 51 objection process for interconnected providers. Direct notice remains for short-term changes and copper retirements, including to 911 service providers and directly interconnecting LECs that support essential 911 functions.
  • Direct notice is due at least 10 days before a short-term network change, 90 days before a planned copper retirement, or 15 days when the copper serves no customer. These notice changes do not themselves authorize service discontinuance or prove that replacement service and 911 continuity are ready.

Analysis

A notice leaves Washington; the network change does not

The change arriving on 15 October is procedural, but its effects are easy to overstate. FCC 26-19 removes filing requirements in the Commission’s network-change disclosure rules and the Bureau’s publication of notices for short-term network changes and copper retirements. It also removes the associated objection process for interconnected service providers. The agency’s October notice confirms the effective date after OMB approvals in September.

The public channel remains. Revised §51.329 lets an incumbent local exchange carrier use publicly accessible industry forums, industry publications or its own website. “Publicly accessible” matters: the order does not describe a notice hidden behind a paywall as an equivalent. What disappears is the FCC docket and agency-issued notice as the standard publication route, not the obligation to tell the public that a covered change is planned.

The direct channel has its own audience and clock. Under §51.333, when an incumbent LEC gives less than six months’ notice of a planned network change, it must serve its public notice on telephone exchange service providers directly interconnected with its network, 911 service providers, and directly interconnecting LECs that support essential functions in affected 911 networks. The rule’s 911 definition reaches providers supplying 911, E911 or NG911 capabilities directly to a public safety answering point or specified local authority, and operators of central offices that directly serve a PSAP.

For short-term network changes, direct notice is due at least 10 days before implementation. A planned copper retirement carries a 90-day direct-notice period, shortened to 15 days only when the facilities are not used to provide service to any customer. For copper notices, a website posting can substitute for service only when the directly interconnected telephone exchange service provider has agreed to receive website postings. The rule also addresses circumstances beyond a carrier’s control that make the waiting period impossible; it calls for notice as soon as practicable and an explanation of the reduced period.

What the rule does not decide

Notice is a way to expose a planned change to affected institutions. It is not the same as a public veto, an FCC finding that a change is safe, or evidence that every recipient has completed a workable transition. The FCC describes Section 251(c)(5) as a notice-based process and says it does not give the Commission authority to prohibit copper retirement under that provision. Removing the formal objection route therefore changes how providers raise concerns; it does not establish that no concern exists.

Nor does a Part 51 notice replace the separate Section 214 process. The FCC says an incumbent LEC still must obtain Commission authorization when a copper retirement or other network change also results in service discontinuance. Part 63 governs that question. FCC 26-19 changes parts of that framework too, but the Part 51 filing change is not blanket permission to stop offering a service.

The FCC also says the Part 51 changes do not create an end-user notice duty; carriers have generally notified customers as a matter of practice. Private contracts may impose their own notice obligations, which the order says remain in force. Customers, local emergency authorities and state agencies may therefore need to look at distinct contractual, statutory and service-discontinuance channels rather than infer protection from the federal network-change notice alone.

The practical test after 15 October is whether the right recipients can find a notice early enough to act. A filing receipt used to show that a document entered a federal process; a public posting shows that information was made available; a direct-notice record shows that named network participants were contacted. None alone proves coordination, a viable substitute, successful migration or continued 911 routing. Those outcomes require their own operational evidence.

Sources