Congress voided the 2016 broadband privacy order whole in 2017, and the bar on reissuing it is still in court

On April 3, 2017, Public Law 115-22 voided the FCC’s 2016 broadband privacy order before its consent and breach rules started. In our reading, its lasting effect was the reissue bar, still before the full Sixth Circuit in 2026.

Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.

Two-minute summaryThe dek and the first sentence of each section, quoted from the article

On April 3, 2017, Public Law 115-22 voided the FCC’s 2016 broadband privacy order before its consent and breach rules started. In our reading, its lasting effect was the reissue bar, still before the full Sixth Circuit in 2026.

  1. The week On April 3, 2017, the President signed Senate Joint Resolution 34, which became Public Law 115-22. [1] The resolution was one sentence long.
  2. The duties: a rule written for carriers, measured against what had started The 2016 order was built around three ideas the summary named: transparency, choice and data security. [2] Each produced a set of duties.
  3. The gap: what the resolution removed and what was left standing A disapproval resolution removes a rule.
  4. The bar: a limit on reissuing the rule, and the argument over what it covers The Congressional Review Act does two things to a disapproved rule.
  5. The buyer: what changed for organizations that rely on carriers Banks, health systems and agencies are carrier customers twice.
  6. How the effects differed by type of organization The resolution applied to carriers.
  7. Objections, in order The duties had barely started, as the stay order and the effective dates show. [2] [3] The argument of this article agrees.
  8. What privacy and technology leaders could check The four parts translate into checks that do not depend on how the Sixth Circuit rules.
  9. With hindsight The first follow-through came on September 21, 2017.

The week

On April 3, 2017, the President signed Senate Joint Resolution 34, which became Public Law 115-22. [1] The resolution was one sentence long. Congress disapproved the Federal Communications Commission rule titled Protecting the Privacy of Customers of Broadband and Other Telecommunications Services, published at 81 Fed. Reg. 87274 on December 2, 2016, and declared that the rule shall have no force or effect. [1] The law’s legislative history records that the Senate considered and passed the resolution on March 22 and 23, and the House passed it on March 28. [1]

The rule it voided was the summary of a Commission Report and Order in WC Docket No. 16-106, FCC 16-148. [2] The Federal Register summary says the order was adopted on October 27, 2016 and released on November 2, 2016. [2] Its purpose was to apply the privacy requirements of the Communications Act, chiefly section 222, to Internet access service and to other telecommunications services. [2]

The order rested on a 2015 decision that Internet access was a telecommunications service under Title II of the Act, which a federal appeals court had upheld. [2] Before 2015, the order explained, those providers had been subject to the Federal Trade Commission’s authority over unfair and deceptive practices. [2] Common carriers are exempt from the FTC’s section 5 authority, so the order said the responsibility for overseeing their privacy practices fell to the FCC. [2]

The summary listed what the rules required. Carriers would give privacy notices and obtain opt-in approval to use and share sensitive customer information, with opt-out approval for non-sensitive information. [2] They would take reasonable measures to secure customer information, and notify customers, the Commission and law enforcement of breaches that could result in harm. [2] Internet access providers could not condition service on a customer giving up privacy rights, and had to give heightened notice and obtain affirmative consent for financial incentives tied to data use. [2]

The order listed eight categories of sensitive customer information, which it described as a minimum. They were financial information, health information, information pertaining to children, Social Security numbers and precise geo-location information. [2] The rest were the content of communications, call detail information, and web browsing and application usage history and their functional equivalents. [2] It covered customer proprietary network information, personally identifiable information and the content of communications that a carrier acquired in providing service. [2]

The breach section was specific. Customers were to be notified without unreasonable delay and no later than 30 calendar days after the carrier reasonably determined a breach had occurred. [2] The exception was a breach where the carrier could reasonably determine that no harm was reasonably likely. [2] A breach affecting 5,000 or more customers was to be reported to the Commission, the FBI and the Secret Service within seven business days, and at least three business days before customers were told. [2] Carriers were to keep records of breaches and notifications for at least two years. [2]

Enterprise customers of telecommunications services other than Internet access got an exemption. A carrier could follow a different privacy and data security regime for them if the contract specifically addressed transparency, choice, data security and data breach, and gave the customer a way to raise concerns. [2]

Very little of this was in force on April 3. The summary made the rules effective January 3, 2017, except for sections whose information collection requirements still needed approval from the Office of Management and Budget. [2] The data security section was set to take effect on March 2, 2017. [2] The notice and choice rules were to take effect on the later of that approval or twelve months after Federal Register publication, and the breach rule on the later of approval or six months. [2]

Then, on March 1, 2017, the Commission granted a stay petition in part. [3] By January 3, 2017 it had received eleven timely petitions for reconsideration, and on January 27 nine trade associations had asked for a stay. [3] The Commission stayed the data security requirements scheduled for March 2 until it could act on the petitions. [3] It did not act on the notice, approval and breach rules, which still awaited approval under the Paperwork Reduction Act, saying it expected to resolve the petitions before those rules took effect. [3]

So the resolution signed on April 3 voided an order whose consent, notice and breach duties had not started and whose security rule was stayed. The practical change for any customer that week was close to nil. The legal change was larger, and it is the subject of this article.

Public Law 115-22 is remembered as the repeal of broadband privacy rules. That description is accurate as far as it goes. It leaves out the feature that mattered after 2017: the way the Congressional Review Act treats a disapproved rule. A rule voided under the Act is treated as though it never took effect, and the agency may not issue a new rule that is substantially the same without new legislation. [4] [5]

Our argument is that the resolution’s lasting effect came from the reissue bar, not from the loss of the 2016 duties. The duties were barely in force when Congress acted. [2] [3] The bar framed the Commission’s 2024 breach rule, which set out at length why that rule fell outside it. [5] In 2026 it was still before a federal appeals court sitting as a full bench. [8]

For banks, health systems and public agencies, the bar matters because their customers, patients and residents reach them through carriers. A carrier’s rules on browsing data and breach reporting decide what a third party knows about those visits and when the organization hears of a carrier breach.

We take the resolution in four parts:

  1. The duties: what the 2016 order would have required of carriers, and how much of it had started.
  2. The gap: what the resolution removed, and what federal law still required of carriers afterward.
  3. The bar: how the Congressional Review Act’s limit on reissuing a rule was read by the Commission and the courts.
  4. The buyer: what all of this meant for organizations that buy connectivity and hold sensitive data.

The first part looks at the rule as written. The second looks at the law left standing once it was gone. The third looks at the constraint on the future. The fourth looks at the organizations on the other side of the carrier relationship. Together they cover what was lost, what remained, what was blocked and who carried the consequences. After the four parts, we look at how the effects differed by type of organization, take objections in order, and list what a privacy or technology leader could check.

A note on sources and our reading. We describe the 2016 rule from its Federal Register summary and the stay from the Commission’s March 2017 order. [2] [3] We describe later events from the Commission’s 2017 removal notice, its 2024 breach order and three Sixth Circuit documents. [4] [5] [6] [7] [8] What these meant for an organization’s contracts and processes is our reading, not a statement of what any law requires of a particular organization. Organizations should check with counsel before relying on it.

The duties: a rule written for carriers, measured against what had started

The 2016 order was built around three ideas the summary named: transparency, choice and data security. [2] Each produced a set of duties. Each also had its own start date, and those dates explain why the resolution changed so little in the short term.

Notice and choice

Carriers would have had to tell customers what information they collected, how they used it and with whom they shared it. [2] They would have had to solicit approval at the point of sale and when they made material changes to their privacy policies. [2] The solicitation had to state the types of information, the purposes, the categories of recipients, and how to reach the notice and the choice mechanism. [2]

The choice mechanism itself was specified. It had to be simple, easy to use, clear and conspicuous, available at no additional cost, and persistently available on the carrier’s website and on any account management app. [2] A customer’s grant, denial or withdrawal had to take effect promptly and stay in effect until changed. [2] The order set the start of these duties at the later of OMB approval or twelve months after Federal Register publication. [2]

The sensitive categories

The heart of the order, for our readers, was the list of sensitive information that would need opt-in approval. Financial information and health information were the first two items. [2] Web browsing history and application usage history were the eighth. [2] Precise geo-location and the content of communications were also on the list. [2]

Put those categories next to each other and a pattern appears. A bank customer who checks a balance from home sends traffic through a carrier. So does a patient who opens a portal, and a resident who files for benefits. The carrier can see which services were reached and when, even where the content is encrypted. The 2016 order would have treated that browsing record as sensitive in its own right. [2] It would also have treated the health and financial information a carrier held as sensitive, whatever its source. [2]

The order did not give banks, health systems or agencies any new duty. It gave their customers a choice over what their carrier did with a record of the visit. That distinction matters later in this article, because the organizations had no say in the rule and no way to replace it once it was gone.

Data security

The data security section was short. A carrier had to take reasonable measures to protect customer information from unauthorized use, disclosure or access. [2] The measures had to account for the nature and scope of the carrier’s activities, the sensitivity of the data, the carrier’s size and technical feasibility. [2] Any lawful security measure could be used. [2]

The order described this as resembling the obligation carriers had been under through section 5 of the FTC Act, and gave carriers a period to revisit their practices. [2] The trade associations’ stay petition argued that the order’s description of the reasonableness standard widened uncertainty for broadband providers relative to other Internet companies. [3] On March 1, 2017, the Commission stayed the section until it acted on the reconsideration petitions. [3]

Breach notification

The breach rule would have replaced the Commission’s existing voice breach rule with a harmonized one for voice and broadband. [2] It set a 30-day outer limit for customer notice, a seven-business-day limit for notice to the Commission and federal law enforcement in larger breaches, and a harm-based exception. [2] It specified what a customer notice must contain, including the estimated dates, the information involved, contact details, and, where there was a risk of financial harm, information about credit reporting agencies. [2]

Its start was the later of OMB approval or six months after Federal Register publication. [2] The Commission’s March 2017 order said it expected to resolve the reconsideration petitions before the breach rule became effective. [3] The rule never started.

What had started by April 3

The summary made parts of the order effective on January 3, 2017. [2] Those parts included definitions and the prohibition on conditioning broadband on a waiver of privacy rights, which the order said would take effect 30 days after publication. [2] The notice, approval and breach sections were waiting for OMB approval, and the data security section was stayed. [2] [3]

In our reading, the honest summary of the 2016 order on April 3, 2017 is a set of duties that existed on paper and had scarcely begun to operate. Customers had not received new notices. Opt-in screens had not been built. No carrier had filed a breach report under the new thresholds. That is why the immediate effect of the resolution was small and its long-term effect was large.

The gap: what the resolution removed and what was left standing

A disapproval resolution removes a rule. It does not change the statute the rule implemented. That was the position the Commission itself took when it later cleaned up the Code of Federal Regulations. [4] Understanding the gap means separating three layers: the statute, the older rules, and the agency with authority over broadband privacy.

The statute stayed

Section 222 of the Communications Act was untouched. The Commission’s own rule text recited that the purpose of its customer proprietary network information rules was to implement section 222. [4] Section 222(a) itself places on every telecommunications carrier a duty to protect the confidentiality of proprietary information of customers, as the Commission’s 2024 order and the 2025 panel opinion both recounted. [5] [7] In our reading, that duty did not depend on any rule.

What a statute without implementing rules means for broadband customers is a legal question we do not answer here. In our reading, it left a general duty with no detailed notice, consent or breach procedure attached to broadband service. A carrier, a customer or a regulator could read that duty in different ways, and nothing in the resolution settled which reading was right.

The older rules came back

On September 21, 2017, the Commission published a document restoring the text of its rules as they read before the 2016 order. [4] It explained that the Congressional Review Act does not direct the Office of the Federal Register to remove voided text, so the Commission had to publish the removal itself. [4] It described the action as effecting what Congress had already done, not as an exercise of rulemaking authority, and said it was not a final agency action subject to judicial review. [4]

The restored subpart was the pre-2016 regime for customer proprietary network information. [4] Its definitions turned on call detail information, telephone numbers and account information. [4] Its breach section was the older rule for voice carriers. [4] Those rules were written for telephone service. In our reading, they did not translate into a framework for broadband browsing records.

The regulator question

The third layer was authority. In April 2017, broadband was still classified as a telecommunications service. [2] Common carriers sit outside the FTC’s section 5 authority, as the 2016 order noted. [2] The resolution did not change the classification. That came later, in the Commission’s 2018 Restoring Internet Freedom Order, which returned broadband to the information service category. [6]

For the months between the resolution and the reclassification, the gap was at its widest. The detailed rules were gone, the older rules addressed voice, and the general privacy regulator of the economy was held back by the common carrier exemption, as the 2016 order had described it. [2] We do not know of any enforcement action that turned on that gap, and we make no claim about how a court would have treated one.

What did not change for the organizations

The sector rules that bind our readers did not move. A bank’s duties under the Gramm-Leach-Bliley Act, a covered entity’s duties under HIPAA, and an agency’s duties under the Privacy Act and FISMA were all unaffected. The resolution concerned carriers only. [1]

The change was in the environment around those organizations. Their customers’ traffic passed through carriers whose privacy and breach obligations had just become less specific. That was outside the organizations’ control and outside their compliance programs, which is the reason it deserved attention.

What the stay had already signaled

The Commission’s March 1 order is worth reading as a forecast. It did not stay the notice, approval and breach rules, but only because they were waiting for OMB approval and the Commission expected to resolve the reconsideration petitions first. [3] In our reading, that told carriers the rules were likely to change before they bit, whatever Congress did.

For an organization watching from outside, the stay was the moment to stop planning around the 2016 rules. A compliance team that had begun to map its carriers against the new breach thresholds had reason to pause in March, before the resolution passed either chamber. [1] [3] The resolution then made the pause permanent.

The bar: a limit on reissuing the rule, and the argument over what it covers

The Congressional Review Act does two things to a disapproved rule. It treats the rule as never having taken effect, which the Commission cited when it restored the old text. [4] And it says the rule may not be reissued in substantially the same form, and a new rule that is substantially the same may not be issued, unless a later law specifically authorizes it. [5]

The second clause is the one that lasts. The Act does not define substantially the same. When Congress voids a long order with several parts, someone must decide whether the bar covers each part, or only the order as a whole. The 2016 privacy order made that question concrete.

The Commission’s reading in 2024

In December 2023, the Commission adopted new data breach reporting requirements, summarized in the Federal Register on February 12, 2024. [5] They expanded breach coverage from customer proprietary network information to all personally identifiable information, and added inadvertent disclosures to the definition of breach. [5] They required notice to the Commission as well as the Secret Service and FBI within seven business days. [5] They removed the duty to notify customers where a carrier can reasonably determine that no harm is reasonably likely, and set customer notice at no more than 30 days after a breach is reasonably determined. [5]

The order addressed the reissue bar directly. The Commission concluded that the bar is best read as prohibiting it from reissuing the 2016 order in whole or in substantially the same form. [5] It said the bar does not prohibit revising breach rules in ways similar to, or even the same as, some revisions the 2016 order had made. [5] The limit, on its reading, applies only where the revisions are the same in substance as the 2016 order as a whole. [5]

The Commission gave three supporting reasons. The resolution named the whole 2016 order. The legislative history, in its review, did not show that the disapproval hinged on the breach provisions. And its new rules differed from the 2016 breach rule in substantial ways in any event. [5] It also observed that congressional disapproval of a particular rule does not nullify an agency’s general authority under the statute. [5]

The panel’s reading in 2025

Trade associations petitioned for review in the Sixth Circuit. On August 13, 2025, a divided panel denied the petitions. [7] On authority, it held that section 222(a) does not give the Commission power to impose breach reporting for personally identifiable information, but that section 201(b) does. [7]

On the Congressional Review Act, the panel first held that the Act’s limit on judicial review did not prevent it from hearing the challenge. [7] It then compared the 2024 order with the 2016 order as a whole and found them not substantially the same. [7] Its reason was that the 2016 order imposed a broad array of privacy rules and the 2024 order addressed only breach reporting. [7] It added that the two would not be substantially the same even if the breach provisions were compared directly, pointing to differences in coverage, notice content and the definition of breach. [7] One judge dissented. [7]

The full court’s order in 2026

On July 31, 2026, the Sixth Circuit granted rehearing en banc. [8] Under the circuit’s rule, that vacated the panel’s opinion and judgment, stayed the mandate and restored the case to the docket as a pending appeal. [8] The clerk was directed to call for supplemental briefs and schedule argument as soon as possible. [8]

As we checked on November 15, 2026, that order is the latest court document we cite in the case. The question the 2017 resolution created, how far the reissue bar reaches, was open before the full court. [8]

What the Commission said the bar still allowed

The 2024 order went further than defending its own rule. It said that, on its reading, the Act would permit the Commission to adopt a breach notification rule that is the same as the 2016 breach rule. [5] It then said its new rule had substantial differences anyway. [5]

That position is broad. In our reading, if it holds, the Commission could rebuild the 2016 order piece by piece, so long as no single action, or combination of actions, amounted to the order as a whole. The order itself considered whether its breach rules, together with its SIM swap and related requirements, came close to that line, and concluded they did not. [5] The challengers’ position would make each piece harder to rebuild. The full court’s answer will decide which reading governs. [8]

Why the bar matters more than the lost rule

A lost rule can be replaced by a new one. A barred rule can only be replaced by Congress. That difference turns a policy reversal into a constraint on every later rulemaking in the same area.

In our reading, the 2016 order’s breadth made the constraint harder to apply. It covered notice, consent, security, breach, financial incentives and enterprise contracts in one document. [2] Any later rule touching one of those subjects could be compared with the whole or with its matching part. The Commission chose the whole; the challengers argued for the part; the panel agreed with the Commission; the full court then vacated that decision. [5] [7] [8]

The bar also reached rules that were not about broadband at all. The 2024 breach order applied to telecommunications carriers, interconnected VoIP providers and relay service providers. [5] It addressed SIM swap rules in its analysis of whether its combined actions were substantially the same as the 2016 order. [5] A resolution aimed at broadband privacy thus became the frame for later voice and relay breach rules.

The buyer: what changed for organizations that rely on carriers

Banks, health systems and agencies are carrier customers twice. Their own networks run on carrier circuits and mobile plans. Their customers, patients and residents reach them over carrier connections. The resolution touched both relationships, in different ways.

The enterprise relationship

For an organization’s own services, the 2016 order had offered carriers an enterprise exemption for services other than broadband access, conditioned on a contract that addressed transparency, choice, data security and breach. [2] In our reading, that exemption was a signal about where enterprise privacy terms belong: in the contract. With the rule gone, the contract was the only place left for them.

An organization that wanted breach notice from its carrier on a stated timeline had to write it in. It had to define what counted as a breach, which data was covered, how quickly notice came and through what channel. The 2016 rule had offered a template for consumers; it gave enterprises none. [2]

The customer relationship

For customers, the relevant data was the record of visits: which bank, which hospital portal, which benefits site, at what time and from where. The 2016 order put web browsing history and precise location on its sensitive list. [2] Without that rule, what a carrier could do with that record depended on the carrier’s own policy and on whatever general law applied.

The organizations could not fix that by contract, because they were not party to their customers’ carrier contracts. They could reduce what the visit revealed. Encrypted connections hide content but not the destination. Domain names, timing and location can still tell a story about a person’s finances or health. In our reading, here carrier privacy rules stop being someone else’s problem.

The breach notice chain

The 2016 rule would have had carriers notify customers within 30 days and federal agencies within seven business days for larger breaches. [2] The 2024 rule kept a seven-business-day federal notice and a 30-day customer notice and widened the information covered. [5] Both rules notified the carrier’s customers. Neither notified the bank, hospital or agency whose customers’ data might be involved. [2] [5]

That gap is structural. A carrier breach that exposes call detail or account data for a bank’s customers could be used for account takeover at the bank. The bank learns of it from the carrier’s public notice, from its own fraud signals, or not at all. No version of the federal carrier rules we cite changed that.

Evidence an examiner or auditor could ask for

Sector examiners do not examine carriers. They do examine how a bank, a covered entity or an agency manages its vendors and its authentication risks. In our reading, a carrier is a vendor like any other for that purpose, and the resolution made the vendor file the main record of what the carrier had agreed to.

The evidence that would answer an examiner’s question is concrete. It is the carrier contract with its breach and privacy terms. It is a risk assessment that names carrier-based factors in authentication and recovery. It is a record of how the organization responded to past carrier breach announcements. And it is a named owner for tracking carrier rules. These items do not depend on the FCC’s rules, which is why they survived every change described in this article.

Second-order effects

The bar also shaped how organizations could plan. A rule that might be revived by the next Commission is different from one that cannot be revived without Congress. In our reading, the resolution moved carrier privacy from a regulatory question that could change with each Commission to a legislative one that would change only with a new statute.

For a compliance team, that meant the stable assumption was the narrow one. Plan for carrier obligations as the restored rules and later orders defined them, watch the litigation, and do not assume that the 2016 categories would return in any form. The Commission’s 2024 order stated its own view of what it could still do. [5] A court’s view could differ. [8]

How the effects differed by type of organization

The resolution applied to carriers. Its effects on our readers varied with how each depended on carriers and which sector rules applied to them.

Banks and credit unions

For a bank or credit union, the exposure ran through authentication. One-time passcodes sent by text message, call-back verification and phone-based account recovery all depend on carrier records. The Commission’s later SIM swap rules addressed one part of that risk for wireless carriers. [5] The carrier records that support those checks were the kind of information the 2016 order had listed as sensitive. [2]

A bank cannot regulate its customers’ carriers. In our reading, the practical response is to treat carrier-based factors as weaker evidence than they appear and to plan for carrier breaches as fraud events. That is a control decision, and it does not depend on what the FCC’s rules say.

Broker-dealers and wealth managers

For firms that record and supervise communications, the carrier relationship is part of the record-keeping chain. The 2016 order’s enterprise exemption, had it lasted, would have let carriers serving those firms on non-broadband services agree to contract-based privacy terms. [2] Without it, the contract still carried the weight. The firm’s own record-keeping duties under securities rules were unaffected by the resolution. [1]

Fintechs and app-based lenders

For firms whose customers arrive only through mobile apps, the carrier relationship is the whole front door. Precise location and app usage history are among the categories the 2016 order would have placed behind opt-in consent when a carrier held them. [2] The firm’s own collection of the same data is governed by its own privacy notices and sector rules, which the resolution did not touch. [1]

In our reading, the risk for these firms was less about privacy and more about fraud. Phone number recycling, number porting and SIM changes feed directly into account opening and recovery. A firm that treats a phone number as identity carries the carrier’s weaknesses into its own controls.

Health systems and ambulatory networks

For health organizations, the visit record itself is sensitive. A connection to an oncology clinic’s portal or a behavioral health telehealth service can reveal a condition. The 2016 order had placed health information and browsing history on its opt-in list. [2] HIPAA governs covered entities and business associates, and the resolution did not change it. It changed what the carrier’s own rules said about the metadata.

In our reading, the response for health organizations is on their side of the connection. Limit what third-party scripts and domains a portal loads. Choose domain names for sensitive services with the patient’s privacy in mind. Assume that destination and timing data is visible to the carrier.

Federal, state and local agencies

Agencies are large carrier customers and large holders of citizens’ data. Their own circuits are bought on contracts that carry their own security terms. Residents reach them over consumer connections. The resolution changed the second relationship, not the first.

For a state benefits agency or a county health department, the record of a resident visiting a benefits or clinic site is the kind of information the 2016 order had put behind opt-in consent. [2] Agencies had no role in that rule and no tool to replace it. Their available response was the same as a hospital’s: reduce what a visit reveals.

Objections, in order

1. The rule never took effect, so nothing was lost

The duties had barely started, as the stay order and the effective dates show. [2] [3] The argument of this article agrees. What was created was the reissue bar, which applied whether or not the duties had started. [5]

2. Carrier privacy is the FCC’s business, not ours

The duties fall on carriers. The data describes the organizations’ customers and their visits. The 2016 order’s sensitive categories named financial and health information. [2] An organization that depends on carrier records for authentication, or whose services reveal sensitive facts by their address, carries part of the consequence.

3. The FTC filled the gap

In April 2017, broadband was still classified as a telecommunications service, and common carriers sit outside the FTC’s section 5 authority. [2] The reclassification that changed that came with the 2018 Restoring Internet Freedom Order. [6] In our reading, on the 2016 order’s own account the FTC’s reach over broadband providers stayed limited while the 2015 classification stood, though how far the common carrier exemption reached was itself a legal question we do not answer. [2]

4. The reissue bar is narrow, as the panel held

The panel held that the 2024 order was not substantially the same as the 2016 order. [7] The full court vacated that decision on July 31, 2026. [8] The width of the bar was therefore unresolved as we checked it.

5. A future Congress can simply authorize a new rule

It can. The Act allows a reissued or new rule that is specifically authorized by a law enacted after the disapproval. [5] That is a higher threshold than a vote of the Commission, which is what the bar is for.

6. Sector compliance programs are unaffected

It does not change their legal duties, as the gap section noted. [1] It changes their risk environment: the reliability of carrier-based authentication, the timing of carrier breach notices, and what a third party knows about a customer visit.

7. A contract cannot do what a rule does

For consumers, that is right. An organization cannot contract on behalf of its customers with their carriers. For the organization’s own services, a contract can set breach definitions, notice timelines and data use limits that bind the carrier. [2] The 2016 order’s enterprise exemption assumed exactly that kind of contract for services other than broadband access. [2] The contract does not replace a rule for the public. It does protect the organization’s own relationship, and it is the one layer the organization controls.

What privacy and technology leaders could check

The four parts translate into checks that do not depend on how the Sixth Circuit rules.

  1. Do our carrier contracts define a breach, the data covered, the notice timeline and the channel, rather than relying on federal carrier rules?
  2. Which of our authentication and recovery steps depend on carrier records, and what is our fallback when a carrier breach is announced?
  3. Which of our public services reveal sensitive facts by their domain names or by the third-party resources they load?
  4. Who in our organization tracks FCC privacy and breach proceedings, and the Sixth Circuit case, and reports changes to the privacy office?
  5. If our sector regulator asked how we assess carrier risk, could we show the analysis?

The checks connect. The first and fourth are about knowing what carriers owe and when it changes. The second and third are about reducing dependence on carriers whatever they owe. The fifth asks whether the analysis is written down, which is where an examiner or auditor would start.

A short exercise makes the point. Take the last carrier breach announcement the organization noticed. Trace when it was learned, by whom, and what changed in fraud controls afterward. If the answer was nothing, the organization has found its gap, and it was there in April 2017 too.

With hindsight

The first follow-through came on September 21, 2017. The Commission published a notice that removed the 2016 text from the Code of Federal Regulations and restored the earlier customer proprietary network information rules. [4] It recorded the dates: Senate passage on March 23, House passage on March 28, and signature on April 3, 2017. [4] It said the notice was not an exercise of rulemaking authority and not a final agency action subject to judicial review. [4]

The second came through classification. The Commission’s 2018 Restoring Internet Freedom Order returned broadband to the information service category, and the D.C. Circuit upheld that determination in 2019. [6] In 2024, the Commission reclassified broadband as a telecommunications service again in its Safeguarding and Securing the Open Internet Order. [6] On January 2, 2025, the Sixth Circuit held that broadband providers offer only an information service, granted the petitions for review and set the 2024 order aside. [6] In our reading, that decision removed the Title II basis on which the 2016 privacy order had rested. [2] [6]

The third came through breach reporting. The Commission’s December 2023 breach order, published in February 2024, expanded its breach rules for carriers, VoIP providers and relay service providers. [5] It became effective March 13, 2024, except for the amended notice sections, which the summary delayed indefinitely pending a separate notice of their effective date. [5] The order set out the Commission’s reading of the reissue bar at length. [5]

The Sixth Circuit panel upheld that order on August 13, 2025, holding that section 201(b) supported breach reporting for personally identifiable information and that the order was not substantially the same as the 2016 order. [7] On July 31, 2026, the full court granted rehearing en banc, vacated the panel decision and restored the case to the docket. [8] As checked on November 15, 2026, we cite no later ruling in the case.

What has held up since April 2017 is the reading this article makes: the resolution mattered more for what it blocked than for what it removed. The duties it voided had barely started. [2] [3] The bar it created has been argued over in a Commission order, a panel opinion with a dissent, and an en banc grant. [5] [7] [8]

What did not hold up was any expectation that carrier privacy would settle into a stable federal framework. Broadband’s classification changed in 2018, changed back in 2024 and was set aside by a court in 2025. [6] Breach reporting for carriers was rewritten and then challenged. [5] [7] [8] The 2016 sensitive categories, including browsing history, financial information and health information, did not return in any federal carrier rule we cite. [2] [5]

The effects on our readers followed the pattern the resolution set. Their own legal duties did not change because of it. Their exposure through carriers depended on contracts they wrote, controls they built and court decisions they could not influence. In our view, that is the right way to read Public Law 115-22 today. It moved carrier privacy from the agency calendar to the court docket and the legislative calendar, where it remained as we checked on November 15, 2026. [1] [8]

One more point held up. The Commission’s 2024 order argued that disapproval of one rule does not nullify an agency’s general authority under its statute. [5] The panel agreed that the Commission had authority under section 201(b), though not under section 222(a), for breach reporting on personally identifiable information. [7] Both statements are now part of a vacated decision and a pending appeal. [8] Organizations that rely on carriers should treat carrier breach rules as contested until the full court rules, and keep their own contract terms as the dependable layer.

Spotted an error? Tell us and we will check it and correct the article where needed.

  • FCC
  • Congressional Review Act
  • broadband privacy
  • breach notification
  • carrier contracts
  • CPNI