Key takeaways

  • The statute is Section 706 of the Communications Act of 1934, 47 U.S.C. 606. Subsection (a) lets the President give priority to communications essential to national defense in a war; (c) lets him, on a proclamation of war or a threat of war, public peril or disaster, or another national emergency, suspend or amend rules for radio stations and devices and close them; (d) gives wire communications similar powers on a proclamation of a state or threat of war, for a period ending no later than six months after it ends.
  • Subsection (e) requires just compensation for use or control, and (g) says the powers do not let the President amend rules the Commission could not lawfully make. The statute does not use the word internet, and commentators disagree about whether it reaches it. Section 706 has not been directly applied to the internet, according to a former FCC commissioner quoted in press coverage.
  • A coordinated total shutdown would be hard in practice: the U.S. internet is thousands of independently run networks, with many interconnections, cables and satellites. Partial and regional disruption by order, by disaster or by attack is a more realistic scenario.
  • The planning conclusion does not depend on the legal debate. A business that can keep operating through a week without internet is protected against the hurricane, the cut cable, the cloud outage and the ransomware attack on a provider, and, as a side effect, against the rare decree.
  • A continuity kit is mostly ordinary: power, local network, local copies of what you need, local tools for the core work, a paper process and a drill. Lawyers have an additional professional reason: competence and confidentiality duties around technology.
  • Claims such as a firm failing within 48 hours of losing the internet are rhetoric, not statistics. Measure your own dependency instead.

The question, asked calmly

Could the United States government switch off the internet? People ask it after storms, after cyberattacks and when governments elsewhere cut connectivity during unrest. It is a fair question, and a business owner is entitled to a sober answer rather than either reassurance or alarm. The answer comes in two parts. One is legal: what the law says a President may do. The other is technical and practical: whether anyone could carry out a nationwide shutdown, and what is far more likely to put a company offline for days. A company's planning should rest mainly on the second part, because the causes there are real, frequent and local.

What Section 706 says

The relevant law is Section 706 of the Communications Act of 1934, codified at 47 U.S.C. 606 and titled War Powers of President. We read it on the Cornell Legal Information Institute site. Subsection (a) applies during the continuance of a war in which the United States is engaged. If the President finds it necessary for national defense and security, he may direct carriers to give priority to communications he deems essential, and carriers that comply are shielded from liability. That is a priority power, closer to the telephone priority services that emergency responders use than to a shutdown.

Subsection (c) is broader for radio. On a proclamation of war or a threat of war, a public peril or disaster, or any other national emergency, or to preserve U.S. neutrality, the President may, if he deems it necessary for national security or defense, suspend or amend the rules for radio stations and devices, order stations closed and their equipment removed, or authorize government departments to use or control them, with just compensation to owners. Subsection (d) gives parallel authority over wire communications, but on a narrower trigger: a proclamation of a state or threat of war involving the United States. Within that period he may suspend or amend wire communication rules, order facilities closed and equipment removed, or authorize government use or control. The period ends no later than six months after the end of the state or threat of war, or an earlier date set by Congress by concurrent resolution.

Subsection (e) provides that the President sets just compensation and certifies it to Congress, that an owner who finds the amount unsatisfactory is paid 75 percent and may sue for the rest. Subsection (g) limits the powers: the President cannot use (c) or (d) to amend Commission rules that the Commission itself could not lawfully make, or to take action whose force would continue beyond the date after which it would no longer be authorized. Notably, the text gives no role to the courts or Congress before action is taken, other than the concurrent-resolution end date in (d) and the compensation process.

Does it reach the internet?

The statute does not mention the internet; it was written for radio and telephone. Whether it can be stretched to cover Internet traffic carried over wires, fiber and wireless is a question lawyers argue about, and it is untested. Press coverage of a former FCC commissioner's warning quotes her saying Section 706 has not been directly applied to the internet, while citing a 2010 Senate report that concluded the President could act against a network if he chose. A bipartisan bill introduced in 2020, the Preventing Unwarranted Communications Shutdowns Act, would have limited the reasons for action and required timely notice to Congress; we could not confirm from the sources we could read what became of it. Commentary also points out that the Act does not define war or national emergency in any way that would constrain a President, and that there is little judicial review. Constitutional questions, including free speech and property rights, would apply to any real attempt, and courts would be asked to decide them in a hurry. These sources are commentary, and we treat their characterizations as one view; this article is not a legal opinion.

Why a total shutdown is practically hard

The U.S. internet is not a single switch. It is tens of thousands of independently operated networks that exchange traffic at many points, carried over many fiber routes, with satellite, fixed wireless and cellular alternatives. Our articles on BGP and anycast describe how these networks interconnect and why routing adapts around failure. A government could order the largest carriers, exchanges and cloud providers to stop carrying traffic, and a partial or regional disruption by order is technically plausible. A complete, clean cut-off of every network, including private ones, universities, enterprises and amateur and satellite links, is another matter. We offer this as engineering judgment, not a quoted finding.

There is an important qualification. Dependence is concentrated. Most companies do not rely on the internet in general. They rely on a few providers: one ISP, one cloud, one identity service, one email platform, one payment processor. Failure or withdrawal of any of them can take a company offline without anything resembling a national shutdown. That is the realistic version of the risk.

What is more likely to knock you offline

  • Hurricanes and floods, which damage power and cable plant for days; firms on the Gulf and Atlantic coasts plan for this each season.
  • Fiber cuts, construction accidents and carrier outages that isolate a building or a neighborhood.
  • Cloud, identity or software-as-a-service outages that leave your systems up but unusable.
  • Ransomware or an attack on a vendor that takes down a provider you depend on.
  • Regional power failures, since every other system, including cell towers, depends on electricity.
  • Rare legal or political events, including the emergency powers above.

The same preparation covers all of them. That is the argument for planning around capability, not around the political scenario. The question to ask is: if our internet connection were gone for a week, which functions would we still need to perform, and what would we need to perform them?

Keeping a business working offline

Start by listing the functions that earn money or carry legal duties: taking orders, issuing invoices, paying staff, answering customers, meeting deadlines, producing the work. For each, note what it depends on today and what the minimum local alternative is. For most firms the list is short, and a continuity kit is built from a handful of ordinary parts.

  • Power: a UPS on the server, network switches and Wi-Fi, a generator interface or a plan for one, fuel logistics and a tested transfer.
  • Local network: a switched LAN that works with the WAN cable pulled, local DNS and time, so that internal systems do not fail when they cannot reach outside names.
  • Local copies of what you need: documents, client data, reference material and software installers, synchronized while online, with an encrypted backup kept offline.
  • Local tools for the core work: file shares, local email and chat between staff, document scanning and search, and printing without a cloud service.
  • Local AI where it helps: a small open-weight language model on an office server can summarize incoming paper, draft letters from notes and extract deadlines, with a person approving everything that leaves the office. Client data stays inside the building. See our articles on running AI without exposing sensitive data and on local models.
  • Paper and people: courier and mail procedures, printed contact lists and a runbook that says what to do in the first hour, the first day and the first week.
  • Alternate links: cellular or satellite as a backup for a few critical functions, understood to be slower and also subject to the same emergency powers and congestion.
  • Drills: pull the WAN cable for a day each quarter and write down what failed.

Clayton Cybernetics packages these parts as an offline-continuity kit, the Apocalypse IT Package, for any business that wants to keep operating through an outage of any kind. The details differ by industry; the architecture is the same.

A worked example: the law office

A law firm is a good illustration because its work is documents and deadlines, and because it has professional duties about technology. A firm that loses connectivity still has to meet filing deadlines, serve clients and protect confidential information. Practically, the kit gives it an offline library of statutes and case law, mirrored while online and searched on the office network; a scanner and optical character recognition that file incoming mail as searchable PDFs; a local drafting assistant; local chat; and a paper e-filing fallback checklist, whose details depend on each court's rules. It is not a substitute for commercial legal research services, which have editorial features such as citators that a bulk mirror lacks.

The ethics rules point the same way. The ABA Model Rules of Professional Conduct, Rule 1.1 comment 8, say competent representation includes keeping abreast of the benefits and risks of relevant technology, and Rule 1.6(c) requires a lawyer to make reasonable efforts to prevent unauthorized access to client information. State rules, including Florida's, adopt versions of these. We could not retrieve the ABA pages while preparing this article, so these descriptions are from our general knowledge and should be checked against the current rules. Continuity planning is a recognized part of reasonable technology practice, and a firm that relies on one cloud provider without a plan for its failure will find the question hard to answer after the fact. Local AI keeps privileged documents on premises, which is a further reason to prefer it for correspondence work.

Other industries have their own versions of the same list. A clinic needs access to patient records and prescriptions, a distributor needs to ship orders and print labels, a manufacturer needs production schedules and safety documents, a financial firm needs positions and client instructions. In each case the method is the same: identify the function, decide the local alternative, practice it.

What to do this month

Write the one-page list of functions and dependencies. Find the single points of failure: the one ISP, the one cloud, the one login system. Buy the power equipment that is cheap and effective. Pull the cable for an hour and see what happens. None of this depends on whether Section 706 can ever be used against the internet. It prepares the company for the outages that will happen.

Sources

This article is general information, not legal advice, and it does not predict any government action. The text of 47 U.S.C. 606 was read in full on law.cornell.edu through a summarizing fetch tool. The commentary about its reach comes from a web-search summary of press and congressional-record items; the Congressional Record PDF could not be read and a JURIST analysis returned an error, so the status of the 2020 bill and the 2010 Senate report cited in press coverage are unverified. The ABA pages returned an access error; the descriptions of Model Rule 1.1 comment 8 and Rule 1.6(c), and of state adoption, are from general knowledge and must be checked against the current rules and The Florida Bar's rules before relying on them. The judgment that a total shutdown is practically hard, the list of likelier causes and the continuity measures are general engineering knowledge, not quoted from the sources listed. The 48‑hour figure sometimes quoted for law-firm failure is not a statistic and is not used here. Last reviewed .

Keep reading

Need help with this?

We run your IT day to day so it stays secure: help desk, devices, Microsoft 365, Exchange, Active Directory, backups, networks and monitoring.

Managed IT Services