A nationwide alert test, three separate technical failures, and a blackout prophecy built from the pieces. Erin and Jake Britt got on their plane. The couple boarded in Washington at 3 p.m. Friday, bound for Fort Lauderdale. At 5:30, they were getting off the same plane in the same city. They left the airport at 8, gave up on the weekend trip, and began trying to recover their money. NPR reported that the wait on JetBlue’s customer service line lasted more than nine hours. Erin set an alarm every 20 minutes so sleep would not cost them their place in the queue. The FAA’s technical problem had become a private night of interrupted sleep.

Image

The Britts had thousands of unhappy companions. A technical problem led the FAA to issue a nationwide ground stop at approximately 3:30 p.m. Eastern on November 13. Departures stopped, while aircraft already aloft continued under established safety procedures. The FAA’s public account says some radio frequencies and radar feeds remained reliable. Approximately 3,500 aircraft landed safely, and air traffic resumed at 8:15 p.m. Operators canceled approximately 12,462 flights that day, although the agency cautions that the ground stop did not directly cause every cancellation. NPR found passengers sleeping in terminal chairs at Tampa the next morning. At Reagan National, a departure board carried delays into the early hours and red cancellation notices. The people in those terminals were still dealing with missed trips on Saturday.

Tuesday’s blackout prophecy borrows a real government event. FEMA and the FCC will conduct a nationwide Emergency Alert System test at approximately 2:20 p.m. Eastern on November 17. Radio and television programming will be interrupted briefly. Cable systems, satellite providers, and wireline video providers are included. The FCC published its formal notice on September 16 and named December 3 as the backup date. A documented worldwide-blackout video uses a darker script: cities lose power, phones fail, elevators stop, and strangers call for help over radios. The fact-checking site Boatos.org preserved that narration while finding no evidence for the forecast. Public records support the test and leave the power failure without a source.

The larger predictions have weaker footprints. A monetary reset to cryptocurrency, a nuclear attack on Iran, and the start of World War III have no documented public mechanism tying them to November 17. I could not verify a common original source for that whole package. No Treasury or Federal Reserve notice announcing a Tuesday conversion appeared in my search on November 16. Nor did a government warning, operational order, or attributable intelligence assessment supporting the assigned war date. Those findings do not promise a peaceful week. The additional war and currency claims remain unsupported for the date assigned to them.

Tuesday’s real event

FEMA’s public announcement uses plain language. It says the message will interrupt radio and television programming and that no action is required. The FCC notice specifies the National Periodic Test event code, distribution in English and Spanish, and reporting duties for participating broadcasters. Its published message includes the sentence, “This is only a test.” The exercise concerns EAS, rather than a nationwide Wireless Emergency Alert to every phone. The announced exercise contains no banking instruction or utility order, and no nationwide phone alert is listed. The test’s public scope is dull enough to be useful. A broadcaster receives a message, retransmits it, and files a report on what happened.

Accessibility gives the procedure a human scale. The November 4 FCC reminder calls for readable visual text and complete audio during the test. Deaf viewers should be able to read the alert. Blind listeners should be able to hear it. Someone watching an ordinary program should know why the tones began and whether anything is expected of them. These are practical obligations, carried by text size, audio playback, and equipment that sometimes fails. The FCC’s reporting process exists because a warning that reaches only part of the audience has left somebody outside it.

Earlier tests left a public trail of mistakes. The FCC’s report on the October 2023 national test says 96.6 percent of participating EAS entities received the message and 93.6 percent successfully retransmitted it. The report describes equipment configuration problems, outdated software, internet difficulties, and accessibility defects. Those figures represent improvement over 2021, with remaining failures laid out in public tables. The alert moves through an internet-based feed and a broadcast relay structure, often called a daisy chain. Nothing in that documented path operates a generator, closes a bank, or changes the denomination of a deposit. A failed receiver would need repair, and the broadcaster’s report would record the failure.

Friday, piece by piece

The FAA has named two possible sources. Its preliminary account says data flooded the FTI network through connection attempts arriving at a rate of 1,000 every four to five seconds. Legacy equipment became unstable, disrupting communications and radar feeds at 17 of 22 Air Route Traffic Control Centers and several terminal radar facilities. Investigators are examining a radar site in Amarillo, Texas, and a radio communications site in El Dorado, Arkansas. L3Harris had been deploying a new router at the El Dorado site. Blocking the two locations stabilized the network, and the same broadcasting function was disabled on approximately 60 similar routers. The FAA says available evidence shows no indication of a cyberattack or outside actor. The FAA and L3Harris say the root-cause work continues.

Microsoft’s trouble started before Friday. Its incident log, mirrored by the University of Pennsylvania, records connection failures across Exchange Online and dependent Microsoft 365 features. Engineers shifted traffic, restarted servers, and tried to preserve a growing backlog of email. The timeout window for delayed messages was extended to 48 hours. Microsoft’s preliminary root cause describes traffic shifts during routine network maintenance and upgrades exposing a latent bug. Requests queued until the affected servers exhausted their processing capacity and stopped accepting new connections. The company found no evidence of malicious activity and promised a preliminary report within two business days, with a final report due within five.

Workday’s failure was easier to exaggerate. The employee platform handles payroll, benefits, time reporting, and other human resources functions for thousands of organizations. A company spokesperson told People that Friday’s disruption affected two data centers and that service was restored by 11 a.m. Saturday. Fox Business reported that Workday discovered a problem while testing backup systems. Walmart and Target are among its large customers. Their customer relationship does not establish that store registers, payment terminals, websites, or every employee account failed. I found no reliable confirmation on November 16 of a nationwide Target payment outage or mass store closures. The verified outage belongs to the employee platform. The stronger retail story remains unconfirmed.

These failures have separate paper trails. FAA investigators describe data flooding and a router deployment. Microsoft describes unavailable servers, a capacity upgrade, and a later network change. Workday reported trouble during backup-system testing. The incidents can share a weekend without sharing a command, a culprit, or a cause. Their public resemblance comes partly from the screen in front of the person affected. A passenger sees a canceled departure. An employee sees a login that will not open. An email user waits for a message caught in a queue. The word “offline” makes those experiences sound identical. The records identify different failures behind it.

The prophecy’s borrowed pictures

A cartoon blackout supplies the pictures. Posts tying the prophecy to The Simpsons point to “It’s a Blunderful Life,” an episode that aired on November 19, 2023. Its story includes a Springfield power failure before Thanksgiving. A review of the viral claim found no documented reference in the episode to November 2026 or American emergency communications. The unidentified social account said to have started the prediction has not been publicly established. That missing origin matters. A scene viewers remember can do the emotional work of evidence before anyone asks who added the date. The claimed connection came from the person holding those two pieces together.

The electrical grid resists that kind of shortcut. Three main interconnections cover the lower 48 states and mostly operate independently. The Energy Information Administration describes numerous balancing authorities managing supply and demand within those structures. Regional failures can cascade, and their consequences can be severe. A simultaneous worldwide blackout is a different claim. It needs a mechanism spanning separate grids, national systems, generators, and operators. The viral narration offers dark cities, stranded elevators, silent phones, and a precise time. It offers no physical means for making those things happen together, only the convenient phrase “the grid,” as if one object were waiting for a single switch. The prophecy never gets as far as naming the equipment that would have to fail.

Cryptocurrency makes the blackout story incoherent. A national monetary conversion would require legal authority and public rules for deposits, debts, wages, taxes, and market settlement. No such Tuesday plan appears in the Treasury or Federal Reserve records I searched. The technical premise also works against the prophecy. Ordinary access to cryptocurrency requires powered devices and communications links, as digital banking does. A wallet on a dead phone cannot make a payment terminal come back to life. Grid failure would interfere with access to both forms of money. It would not perform the conversion that the prediction leaves unexplained.

Iran exposes the limit of a fact check. No public evidence supports assigning a nuclear strike on Iran or the beginning of World War III to November 17. That is the available answer, and it is narrower than a guarantee. Governments can make decisions in secret. Wars can begin without an internet prophecy warning us first. The claim before us still needs evidence connected to its date, and none has been produced. Nuclear danger deserves serious reporting even after a fabricated timetable has been discarded.

Pattern research offers a modest explanation. In a 2018 series of experiments, Jan-Willem van Prooijen, Karen Douglas, and Clara De Inocencio studied illusory pattern perception with random coin-toss sequences and chaotic paintings. Seeing patterns in unstructured material predicted stronger conspiracy belief in several experiments. The authors treated this as one cognitive mechanism and noted limitations in their work. Their findings do not diagnose every person who wonders whether officials are telling the truth. They describe a familiar mental move under uncertainty. Several events occur close together, the mind tries the connection, and a story begins to feel like knowledge. Friday the 13th and a federal countdown make that move easier.

Erin Britt described the human part better. She told NPR that the pilot and flight attendants had no more information than the passengers. “They seem just as in the dark,” she said. Her sentence contains the part of Friday that a technical summary cannot hold. The people responsible for explaining the delay were waiting for an explanation too. A hidden cause leaves room for embarrassment, anger, and suspicion. It also leaves a traveler setting alarms through the night because a technical failure has become a refund that has not arrived. Conspiracy stories promise to identify the hand behind that disorder. The FAA and airline systems recovered before every passenger’s plans did.

What Friday exposed

Concentration hides inside ordinary procurement. Workday serves more than 11,500 customers globally, according to the company figure reported by People. Microsoft 365 sits inside businesses, schools, agencies, and homes that have no other meaningful connection. The FAA’s telecommunications network links facilities across the country. Administrator Bryan Bedford said all facilities rely on one network and warned of “no backup to the backup”. A failure at one supplier can therefore wear thousands of familiar names in a single afternoon. Outsiders see Walmart, Target, Netflix, Southwest Airlines, and city governments in the same outage story. The shared vendor is less visible until somebody looks for it. That dependence deserves attention because a single technical problem can interrupt unrelated kinds of work. It does not require coordination among the organizations feeling the effects.

Modernization was underway when the FAA system buckled. Transportation Secretary Sean Duffy told reporters that L3Harris had been doing routine work converting copper lines to fiber optics. L3Harris says it has completed more than 70 percent of those conversions and is supporting the FAA investigation. Congress approved $12.5 billion in July 2025 for air traffic control modernization, according to NPR. Duffy was asking for more money on Saturday while passengers were still sleeping in terminals. The old system needed replacing, and the replacement work may have played a role in the failure. The FAA must keep aircraft moving while that conversion continues.

Recovery systems deserve scrutiny too. Microsoft’s account describes failed servers placing more demand on the machines left standing. The FAA’s account describes connection attempts flooding legacy equipment. Workday discovered its problem while testing backups. Each case involves a safeguard or improvement that met real operating conditions. Extra capacity has to remain available when traffic surges. Backup tests should protect the service without damaging it. Older networks add their own risks when a router is replaced. Friday exposed weaknesses in the protective measures themselves, and those weaknesses belong in the repair reports.

The next useful documents are post-incident reports. Microsoft has promised one, with a timeline and repair items. The FAA and L3Harris still need to establish the exact error that began the data flooding. Workday’s customers need to know how backup testing affected two data centers and what has changed since restoration. The FAA’s detailed question-and-answer page is a better start than a bare assurance that safety comes first. Its details can be checked, challenged, and revisited. Corporate and government investigators should be held to that standard even when they conclude that nobody attacked them. Their customers and the public should be able to read what failed and what changed.

Tuesday does not require a survival ritual. The announced test asks nothing of the public. Ordinary household preparation remains useful without a countdown. Ready.gov recommends water, nonperishable food, medications, a flashlight, batteries, a charger, and a battery-powered or hand-crank radio, among other supplies. Those things help during a winter storm or a local outage. A small amount of cash can help when card payments fail. None of these preparations requires believing that the world will go dark at a scheduled second. The supplies can remain in a closet after Wednesday, ready for a storm that has nothing to do with this rumor.

I keep returning to those 20-minute alarms. Erin Britt was afraid sleep would cost her place in the refund queue. After a wasted day, that fear made sense. It had nothing to do with a cartoon or a secret monetary reset. A real failure reached her Friday, and she was still dealing with it after she left the airport. I expect Tuesday’s alert to interrupt a broadcast and identify itself as a test. Then I expect to go back to work. The FAA investigation, Microsoft’s report, and Workday’s explanation will be waiting, and I expect to read them when they arrive.

Reporting current as of November 16, 2026. The FAA, Microsoft, and Workday investigations and post-incident reviews may add material facts after publication.