The FCC copper sunset: what does the 31-day rule mean if you still have POTS lines?

By Michael Obraitis, Managing Partner, and Michael Dale, CEO · Published August 17, 2026 · Last reviewed August 2026 · ADAM Pulse Knowledge Base · Carrier Transition Series

Short answer

The FCC has made it faster and simpler for carriers to retire legacy services. It has not set a national date on which copper stops working, and the 31-day figure is not a countdown on your phone line.

The two things worth knowing:

1. The 31 days is the FCC's clock, not yours. It is the period after which a discontinuance application is automatically granted unless the Commission intervenes. That grant is permission for the carrier to proceed. Your actual cutover date comes from the carrier's own notice.
2. You should already have that notice before the clock starts. Under 47 CFR § 63.71(a), the carrier must notify affected customers in writing before it files with the Commission, and the notice must state the planned date of discontinuance.

So the honest framing is not "you get 31 days." It is: the written notice is your real warning, it arrives before the federal process even begins, and the federal process is now short enough that there is no slack behind it.

The lines that hurt are rarely the phones. They are the analog circuits nobody has thought about in a decade: fire alarm panels, elevator emergency phones, blue-light phones, gate and entry systems, fax, security panels, modems and telemetry.

What FCC 26-19 actually is

The order is "Reducing Barriers to Network Improvements and Service Changes; Accelerating Network Modernization", WC Docket Nos. 25-209 and 25-208, adopted 26 March 2026 and released 27 March 2026.

It is widely referred to as the Network and Services Modernization Order, including in the FCC's own March 2026 fact sheet. If you cite it, use the released title above and the document number — the fact-sheet name will not match what a reader finds.

What it does:

Why the codified rule still says 60 days for dominant carriers

The order and the codified rule do not currently say the same thing. The reason is not what it looks like, and it changes what you should do.

As of 17 August 2026, the text of 47 CFR § 63.71 on eCFR still shows the 31-day automatic grant for non-dominant carriers and a 60-day period for dominant carriers.

That is not a codification lag. It is the operative rule.

FCC 26-19 was published in the Federal Register at 91 FR 20938 on 20 April 2026, with a general effective date of 20 May 2026. But the amendatory instruction that revises § 63.71 — instruction 10 — is one of several delayed indefinitely, and the Commission stated it would publish a separate Federal Register document announcing the effective date. That document has not appeared as of this writing.

So the unification to 31 days for all carriers is adopted but not yet in force for § 63.71. eCFR flags the pending amendment but has not changed the section text, which is correct behaviour rather than a delay in updating.

The practical consequence is the opposite of what a codification-lag reading would give you. For a dominant carrier's discontinuance application today, 60 days is still the rule. Do not plan around a 31-day clock for a dominant carrier until the Commission publishes the effective date. Cite FCC 26-19 for what the Commission has adopted, and cite the codified section for what currently binds.

This is the second time in this subject area that the operative date has lived in a different document from the order that created the rule. The Kari's Law dispatchable location compliance dates were not in Report and Order 19-76 either; they were announced separately at 85 FR 78018. If you follow FCC rulemakings, the adopting order tells you what was decided and a later Federal Register notice often tells you when it starts.

When the 31-day clock actually starts

This is the part that gets reported wrong in both directions, and the rule resolves it in a way neither simple answer captures.

47 CFR § 63.71(f)(1) says an application "shall be automatically granted on the 31st day after its filing with the Commission without any Commission notification to the applicant unless the Commission has notified the applicant that the grant will not be automatically effective."

Read that alone and the clock starts when the carrier files. But the same section adds:

"For purposes of this section, an application will be deemed filed on the date the Commission releases public notice of the filing."

So both are true. The rule says "after its filing", and separately defines filing as the date of the Commission's public notice. The practical effect is that the 31 days runs from public notice, and the mechanism is a deeming provision rather than a policy choice between two options.

That distinction matters if you are citing this. Saying "the FCC chose public notice over filing" describes a debate the order does not record. Saying "the rule deems an application filed on the date of public notice" is what the text supports.

The sequence, in order

1. The carrier notifies affected customers in writing — § 63.71(a). The notice must state the planned discontinuance date.
2. The carrier files the application with the FCC.
3. The FCC releases public notice of the filing — the application is "deemed filed" from this date.
4. 31 days run — this is the objection window.
5. Automatic grant, unless the Commission removes the application from streamlined processing.
6. The carrier discontinues on its own schedule — the date from step 1, not 31 days from anything.

Step 1 is the one to internalize. The written notice is a precondition of filing, not a consequence of it. If a notice is on someone's desk, the federal clock has probably not started yet — and step 4 is your window to object.

Does this mean my line shuts off in 31 days?

No, and treating it that way will misdirect the work.

The automatic grant authorizes the carrier to discontinue. It does not perform the discontinuance. Your date is in the carrier's notice, which by rule you receive before the application is filed.

Two opposite errors to avoid:

"Everything copper dies on one national date." It does not. There is no such date.

"It still works, so it will keep working." Also wrong, and more expensive. Between blanket grandfathering and a streamlined 31-day process, the direction is unambiguous even without a deadline.

There is a subtler trap inside grandfathering. Blanket authority lets a carrier keep serving existing customers while closing the service to new orders. So a line that still works at your current building may be unavailable for a new building, an expansion, or a like-for-like replacement after a failure. The service can be alive at one address and unobtainable at the one next door.

Why the phones are not the problem

A company can run every employee on a cloud platform and still hold a rack of analog lines. Migrating staff voice and migrating specialty analog equipment are different projects with different constraints, and only the first one usually gets a project plan.

The inventory that tends to be invisible:

The governing principle: regulatory adequacy is not technical compatibility. A replacement that satisfies the FCC's framework as an adequate replacement service says nothing about whether your fire panel will communicate over it. Those are different questions answered by different people.

That applies to the 5/1 Mbps wireless category too. Its presence in the order means it counts as an adequate replacement for the discontinuance analysis. It does not mean a given device will work on it.

On analog telephone adapters

An ATA presents an analog interface to an IP service. That is not proof that a specialty device will work reliably or satisfy the requirements that apply to it. For fire panels, elevator communications, life safety devices and specialty modems, verify with the equipment vendor and the authority having jurisdiction rather than with a dial tone test.

The question nobody asks until it is too late

Traditional analog service drew power from the central office, which gave compatible simple phones a useful independence from the building's electricity.

Most replacement paths do not. They depend on locally powered equipment: ONTs, modems, routers, firewalls, switches, gateways, cellular devices. Every one of those is a thing that stops when the power does.

So evaluate two states, not one:

• Does the replacement work normally?
• What happens when commercial power fails, and for how long?

The same logic applies to connectivity. An IP replacement depends on a chain — device, gateway, LAN, firewall, internet, provider — and each link is a failure point that the old copper pair did not have. Depending on the application, that may require redundant internet, cellular or fixed wireless backup, UPS, or a generator. Satellite links such as Starlink can be part of an architecture, but they are connectivity, not an analog line replacement.

What to do before a notice arrives

The carrier's notice should confirm a project you already understand, not reveal a dependency you did not know you had.

1. Pull every carrier invoice, across every provider and every site. A bill will tell you a number exists without telling you what it does.
2. Build one inventory, centrally. Multi-site organizations otherwise discover the copper sunset one branch at a time.
3. Physically identify what is on each line. Records get you most of the way; the last stretch is a walk to the demarcation point.
4. Separate life safety from convenience. Fire, elevator, emergency and security first. Do not migrate an easy fax machine while an unidentified elevator circuit sits unresolved.
5. Never disconnect a line because nobody recognizes it. Alarm reporting, elevator calls, monthly modem polling and after-hours security events are all quiet most of the time. Unknown does not mean unused.
6. Route carrier notices to the right person. They arrive at accounts payable, a branch manager, or a billing contact who left in 2019. Anything mentioning discontinuance, retirement, copper, analog service or network modernization needs to reach the telecom owner the day it lands.

That last one is the cheapest control on this list and the one most often missing.

Frequently asked questions

Related articles

• How do you find every POTS line your business still has? — the audit procedure. In preparation.
• POTS replacement for fire alarm panels and elevator phones: what actually works. In preparation.
• You got a copper discontinuance notice. What are your options and your deadline? In preparation.
• Internet redundancy best practices — the resilience side of any IP replacement.
• Dual WAN and internet failover monitoring — proving the backup path actually works.

References

Primary sources first. The order is the rule change; the CFR is the codified text; the carrier's notice governs your dates.

1. FCC 26-19 — Reducing Barriers to Network Improvements and Service Changes; Accelerating Network Modernization — WC Docket Nos. 25-209 and 25-208; adopted 26 March 2026, released 27 March 2026. Cite this for the unified 31-day period.
2. 47 CFR § 63.71 — Procedures for discontinuance, reduction or impairment of service by a domestic carrier — the codified text. Checked 17 August 2026; still shows 60 days for dominant carriers.
3. FCC — Domestic Section 214 Discontinuance of Service — orientation only; not a primary source.
4. Your carrier's discontinuance notice and application — the only source that carries your actual dates. Obtained per account; no public URL.
5. Equipment manufacturer and specialty system vendor documentation, plus applicable local codes and AHJ requirements — obtained per site and per device; no public URL.