Thursday, November 19, 2026

Farm Payments Frozen: USDA Takes Systems Offline After a Cybersecurity Incident


 

The week of American tech trouble just reached the farm. The U.S. Department of Agriculture has taken numerous applications offline over several days after its own security team found what it called a "security incident," Nextgov/FCW and Government Executive reported Thursday afternoon, Nov. 19, 2026. The outages have hit many of the financial tools USDA uses to move payments between the department and farmers.

As of 6:15 p.m. MST (Arizona time), Thursday, Nov. 19, 2026. USDA has not publicly confirmed a breach, no one has said who was behind it or whether any data was stolen, and no restoration timeline has been announced.

via @WatcherGuru on X

"Reset all database passwords"

According to Nextgov/FCW, the trouble traces back to an internal email sent Monday by Chris Rottler, acting assistant chief information officer for USDA's Farm Production and Conservation Business Center. The email said the department's Cybersecurity and Privacy Operations Center had "uncovered a security incident" that required its Information Services Division to "reset all database passwords in all environments, and this is requiring us to reset all applications causing outages."

Nextgov said a technical bulletin dated Thursday warned that maintenance was ongoing and that applications "may continue to experience intermittent outages throughout the week." By late Thursday afternoon, some staff were also having trouble with the department's virtual private network (VPN), according to one source and a separate notice the outlet viewed. Nextgov said it was not clear whether every employee received the Monday email, and that USDA and the Cybersecurity and Infrastructure Security Agency (CISA) had been asked for comment.

via @HormuzLetter on X

Why farmers should care

USDA gives farmers a financial safety net, including crop insurance and help covering losses when bad weather cuts harvests. Nextgov reported that the outages have affected many of the tools behind those payments, and that staff have been unable to reach key client-facing applications used to check notifications and the status of loans and other aid.

Farm trade outlet DTN/Progressive Farmer reported that software used by local Farm Service Agency (FSA) and Natural Resources Conservation Service offices has had intermittent outages since Monday, disrupting some work on producer loans and payments. Affected employees reported internal guidance to "proceed with caution and don't do any critical work," and users also reported problems with USDA's eAuthentication login system, DTN said. As of Thursday afternoon, a county loan officer told DTN the problem was still there.

The timing is awkward. DTN noted that producers have until Dec. 11 to enroll in the 2026 Agriculture Risk Coverage and Price Loss Coverage programs, and dairy producers have until Dec. 18 to enroll in the 2027 Dairy Margin Coverage program.

Officials play it down

USDA leaders did not call it a breach when DTN asked. FSA Administrator Bill Beam said, "I have heard that there's some outages. I talked to our leader in the IT department, and you know they're working on it." Richard Fordyce, USDA's undersecretary for farm production and conservation, said, "We will occasionally have outages sometimes because there's updates."

Inside the department, frustration is growing. Nextgov's sources said senior officials have not kept staff fully informed, and one said they had only been given vague information about a possible security breach.

via @InsiderWire on X

Another week, another outage

The USDA news lands on top of a string of disruptions this month, including the NSA's NSANet outage and Thursday's vendor breach tied to Chase, Visa and Mastercard. Nextgov said some USDA staff worried the department could be the next to suffer widespread IT problems, after recent incidents that were not cyberattacks hit aviation networks, financial systems, Microsoft tools and the NSA. DTN reported that on Wednesday, intelligence officials told Congress those recent outages were separate incidents tied to maintenance and technical changes, not a coordinated cyberattack.

DTN also pointed to a Government Accountability Office report released Thursday finding that USDA and the Food and Drug Administration have not fully put in place 16 federal requirements meant to improve cybersecurity across the food and agriculture sector, including emergency preparedness and sharing real-time threat information with CISA. USDA disagreed with GAO's recommendations, DTN said. Times Now also covered the incident.

We'll update this story if USDA confirms what happened, names a culprit or says when farmers' payment systems will be fully back.

Hacked Through the Side Door: Vendors for Chase, Visa and Mastercard Breached, Customer Emails Leaked


This week's run of tech trouble has a new chapter, and this time it's a hack. On Thursday, Nov. 19, 2026, JPMorgan Chase said outside companies that do work for the bank were hit by a cyberattack, and that the attackers may have gotten customer names and email addresses. Visa and Mastercard also said third-party providers they use were involved. A cyber extortion group calling itself "n0n" has claimed the attacks and posted data online, Reuters reported.

As of 11:15 a.m. MST (Arizona time), Thursday, Nov. 19, 2026. None of the three companies has named the vendors that were breached, and no one has said how many customers were affected.

What Chase said

Chase posted its statement on X at about 6:17 a.m. Arizona time. "Based on our investigation so far, we believe the attackers accessed certain marketing data held by those vendors, which may include some customer names and email addresses," the bank said. Chase also said "there is no disruption to our services" and that "where appropriate, we will contact affected customers directly and offer support, including complimentary credit monitoring," according to The Verge, which published the full statement.

via @Chase on X

The bank also said, "There is no connection to service disruption some customers experienced earlier this week." That refers to Monday's Chase outage, which the bank blamed on a software bug. ABC News noted that JPMorgan did not say when the cyberattack happened or name the third-party companies involved.

What the hackers claim

According to Reuters, n0n claimed on Nov. 16 that it had cardmember engagement records with "hundreds of thousands of campaign interactions for tens of thousands of distinct cardmember email addresses." Reuters cited a screenshot captured by the cybercrime research platform eCrime.ch. In its own review of the posted data, Reuters found what appear to be 124 bank employee email addresses and more than 16,000 customer email addresses, some with phone numbers and postal codes. Reuters said it could not independently verify that the data is authentic, and JPMorgan declined to comment on the data.

Cybernews, which has followed the gang's claims since Nov. 17, said n0n gave the companies a 48-hour countdown to negotiate before dumping the files. Its researchers said the JPMorgan leak covers roughly 16,000 customer email addresses, phone numbers in some cases and JPMorgan Chase account IDs. They said it appears linked to the bank's invitation-only Reserve card program.

via @Cybernews on X

Visa and Mastercard: no card numbers

A Visa spokesperson told Reuters the claims are "associated with an incident involving a third-party service provider in Asia Pacific. Visa's systems were not involved and were not impacted. No payments data such as card numbers were affected." Reuters said the Visa files focus mostly on Asia-Pacific markets such as Hong Kong, Taiwan, Korea, Japan and Australia. Cybernews counted more than 6,000 premium Visa customers in the leak, likely from a platform that tracks Visa's premium dining programs in the region.

A Mastercard spokesperson told Reuters the company was recently informed of an incident "at a third-party provider that resulted in the exposure of limited amount of email addresses — non-payments information — from a small subset of cardholders enrolled in a specific benefit program." It added, "There is no impact to the Mastercard payment network or the ability for people to use their cards." Cybernews said the Mastercard leak has about 2,000 customer entries, if authentic. A Cybernews researcher said all three datasets share similar formatting, which suggests they may have come from the same third party. That hasn't been confirmed.

via @WatcherGuru on X

Who is n0n?

Reuters, citing eCrime.ch, said the group has claimed roughly 200 incidents since it showed up in September 2026. Cybernews reported that the gang recently claimed travel giant Expedia too. The Washington Post and Quartz also covered the breach, with Quartz citing The Wall Street Journal.

What customers should do

If you're a Chase customer, watch out for scams. Dr. Pablo Molina, head of cybersecurity at Drexel University, told NBC10 Philadelphia that people should be careful with messages that look like they come from Chase but arrive from unfamiliar phone numbers or email addresses. He also suggested freezing your credit if you think your information was exposed. "Customers don't distinguish between a bank and a vendor when it comes to a cyberattack," consultant Carissa Robb of SolomonEdwards told Reuters.

Still unconfirmed

Several key questions are still open. The vendors haven't been named, and nobody has said how many customers were affected or when the break-in happened. Reuters and Cybernews both say they couldn't verify the leaked files. Nobody has confirmed that one vendor was behind all three leaks. We'll update this post as the companies share more.

It Flew on His Wing: 62 Years Since a Navy Destroyer and a Crusader Jet Chased a Dark Delta Off Puerto Rico

Sixty-two years ago tonight, somewhere over the moonlit Caribbean, a U.S. Navy pilot looked out his left canopy and saw something he could not explain sitting nine miles off his wing, matching his speed, his altitude and his heading as if it had been invited to fly formation.

It was the evening of November 19, 1964. What happened over the next 21 minutes ended up in Project Blue Book's files, set off a flurry of military message traffic, and was still being picked over by the CIA months later. It's one of the cases that UFO researchers keep coming back to, because it has nearly everything: a radar track, a trained pilot's eyewitness account, radarscope photographs, and even a brief spell of radar jamming nobody could pin on anyone.

A ship testing a new radar

The first detection didn't come from the jet. It came from the destroyer USS Gyatt (DD-712), which was at sea about 220 miles northwest of Puerto Rico running trials for the Navy's Operational Test and Evaluation Force. On board was a prototype AN/SPS-49 search radar, and the crew was recording its screen with a shipboard radarscope camera, a lucky detail, because it meant the night was being photographed.

Around 9 p.m. local time, the Gyatt's radar picked up a "bogey." The ship was working with an F-8 Crusader from Utility Squadron Eight (VU-8) out of Naval Station Roosevelt Roads, call sign "Salt Spray 26," which was cruising at about 30,000 feet over Puerto Rico. Communications were poor (the pilot later blamed working UHF radio at around 230 miles), but the Gyatt warned him something was out there, and around 9:01 p.m. he reported "a stranger closing very fast."

The delta that joined up

The pilot was the squadron's executive officer, a lieutenant commander with extensive jet experience, named in the records as K.H. Woodbury (some summaries spell it "Woodsbury"). The weather, by the Air Force's own message, was "clear, visibility good, with full moon."

In his written answers, he described a single object: a delta shape, "about size of operational fighter (F4)," dark black or gray, with no navigation lights and no contrail, just what looked like a single afterburner-style light glowing from its tail when it accelerated.

According to his report, it flew overhead at very high altitude and very high speed, swung around, came back past him on a parallel course, and then "circled to right around observer and joined up at about 8 or 9 miles in 9 o'clock position," holding about Mach .84 at 30,000 feet, the same as him. He lit his afterburner and tried to turn in and close the distance. His one-word verdict on that: "(Unsuccessful)." The object pulled away in a wide climbing turn, going up through 50,000 feet at a steep angle in excess of Mach 1.

And it wasn't done. On and off, the encounter lasted about 21 minutes, and on his way home to Roosevelt Roads, the object reportedly closed on him again from behind.

NICAP's case summary quotes his assessment: "Its speed, acceleration, ceiling and ability to de-cellerate exceed any aircraft I have ever seen or heard of. There is no reasonable explanation for this target." During the encounter, the Gyatt's SPS-49 was also briefly jammed, and the source was never identified.

How fast was it, really?

Here's where it gets messy, in a good way. A Caribbean Sea Frontier message reported the pilot's estimate as "in excess Mach 3" and said the Gyatt's radar had tracked the object at more than 3,800 knots, roughly 4,370 miles per hour.

When the Air Force's Foreign Technology Division analyzed the radarscope photos, it came up with a much tamer picture: the bogey cruised at subsonic speed for the first stretch, then accelerated, averaging about 1,200 knots and, per the photos, never topping about 1,515 knots. Blue Book's final call was simply "Aircraft." Even the squadron's own evaluation leaned that way: it judged the target a "very high performance aircraft" because it maneuvered like one, apart from that extreme acceleration, deceleration and steep high-speed climb.

Not everyone bought it. Researcher Antonio Rullan later re-worked the same scope data and argued that it supports the ship's original claim, that the bogey was supersonic for most of the track, hit around 1,500 mph, and then slowed to about 260 mph once it had shaken off its pursuer.

Not the only night

The Gyatt incident wasn't a one-off. An intelligence officer at Ramey Air Force Base reported that the same people had picked up unidentified radar contacts on November 16, 17 and 18, and again on the 24th. A 1965 CIA document on the episode concluded there were "apparently valid tracks and/or observations of unidentified aircraft" around the Atlantic Fleet Weapons Range on several of those dates. Researcher Joel Carpenter has also pointed to Blue Book teletypes suggesting the Air Force chief of staff ordered an investigation under pressure from the White House.

So whose was it? That's the fun "what if," and it's pure speculation: a secret U.S. test aircraft that nobody told the Navy about? A foreign intruder probing the range? Or something that didn't come from anyone's hangar at all? Officially, it was an unidentified aircraft. Unofficially, a veteran Navy pilot couldn't catch it, and couldn't explain it.

Sixty-two years later, the nineteen radarscope photos sent to Blue Book still haven't surfaced publicly. Somewhere, maybe, a dark delta is still flying on somebody's wing.

Sources: NICAP RADCAT case directory and Antonio Rullan's report; Project Blue Book case file; CIA document via The Black Vault; UAP Globe case file.

Wednesday, November 18, 2026

Streaking Past the Window: A Passenger's LaGuardia Video Leads NewsNation's Airport UFO Roundup

Look out your airplane window and you might catch more than the skyline. In this new NewsNation compilation, posted November 17, 2026, the standout clip is passenger Michelle Reyes's window video of a cylinder-shaped object streaking past her plane near LaGuardia Airport in New York. Investigator Ben Hansen estimates it was moving at more than 200 mph and says he found no evidence it was faked, while the rest of the segment revisits drones swarming over Long Island's Gabreski Airport and the airspace closures around El Paso.

Nothing here has been officially identified, so treat it as unexplained footage, not proof of anything otherworldly. UFO, drone, or something else entirely? Watch and decide for yourself.

Video: "Airport Sightings: UFOs or Drones Watching Our Skies? | Backscroll" by NewsNation on YouTube.

Cart Crash: Amazon App Outage Hits Thousands of Shoppers as Tech Breakdowns Keep Piling Up

First it was Microsoft, then the FAA, Chase, United, Apple and the NSA. On Tuesday, Nov. 17, 2026, it was Amazon's turn. Thousands of shoppers reported problems with Amazon, most of them with the Amazon mobile app, according to outage tracker Downdetector. Reuters reported that Downdetector showed more than 5,000 reports of issues with the shopping platform as of 6 p.m. Pacific time (7 p.m. Arizona time).

As of 11:30 a.m. MST (Arizona time), Wednesday, Nov. 18, 2026. Outage trackers show Amazon reports back near normal levels, but Amazon has not publicly explained what happened or confirmed a fix.

What went wrong

Downdetector's own account flagged the problem on X Tuesday evening, saying user reports indicated problems with Amazon "since 12:21 PM EST," which is 10:21 a.m. Arizona time. The big wave of complaints came later in the day. Downdetector's post went out at 6:21 p.m. Arizona time, and Reuters' 5,000-report count came about 40 minutes later.

via @downdetector on X

Another tracker, Instatus, recorded reports for Amazon jumping to a peak of 11,425 an hour, more than 60 times normal. By its count the spike lasted about 13 hours, starting in the 10 a.m. hour Arizona time on Tuesday and returning to normal around 11 p.m. Users who left comments there wrote "Not loading" and "Can't log in." Most reports were about the mobile app rather than the website.

Shoppers took to X as the evening went on. Financial news feed First Squawk posted that "Amazon experiences reported service issues as user complaints increase on Downdetector." A widely shared post from the account Anonymous TV described a "possible widespread Amazon outage" hitting the website, mobile app and checkout. That post has drawn more than 1,000 likes.

via @YourAnonTV on X

What Amazon has said

So far, nothing we could find. We didn't find any public statement from Amazon about the cause, how many customers were affected, or whether the problem has been fixed. Instatus lists Amazon's official incident note as "Nothing posted" and says it couldn't find an official status page for Amazon's shopping site. Reuters' report also didn't include any comment from the company. Until Amazon speaks, the cause is unknown. There's no confirmation either way about whether it was a software problem, a cloud issue or anything else.

via @FirstSquawk on X

Is it fixed?

The trackers suggest that things have mostly calmed down. On Wednesday morning, Instatus's live Amazon page said "No, it's up," with 55 reports in the past hour. Most of those were still about the mobile app. LiveOrDown, which only checks whether the website loads, found Amazon.com reachable from all three of its test regions at about 11:08 a.m. Arizona time. That's not the same as Amazon confirming a fix. India's Sunday Guardian Live cited Downdetector readings of 2,051 reports against a normal baseline of 14, later easing to 328. It said users described the app failing to load, "403" access-denied errors and trouble reaching orders and account pages.

What about Audible? We couldn't confirm a widespread Audible outage. LiveOrDown logged only three Audible app reports Tuesday evening, and another tracker showed no Audible reports during the same window.

Not Amazon's first stumble this year

Amazon has had a bad outage before. On March 5, 2026, Reuters reported that its website was hit by an outage that peaked at more than 22,700 Downdetector reports. Amazon later said that problem was related to "a software code deployment". There's no word yet on whether Tuesday's trouble had anything in common with that one.

A week of breakdowns

Tuesday's Amazon trouble came at the end of a remarkable run. CNBC counted Microsoft's Outlook problems on Thursday, the FAA ground stop on Friday, Monday's issues at JPMorgan Chase and United Airlines, and Tuesday's Apple outage and NSA network failure. Director of National Intelligence Jay Clayton told CNBC, "This is not cyberattack, and this is not a coordinated effort by a nation state. We've looked very closely." His comments came before Amazon's trouble peaked, and nobody has tied Amazon's outage to the others.

If your order history or checkout broke Tuesday night, you weren't alone. We'll update this post if Amazon explains what happened.

It Turned Inside His Plane: 78 Years Since a Glowing Oval Ran Rings Around a Pilot Over Andrews Air Force Base


Long before the famous 1952 "invasion" of Washington's skies, and more than half a century before Navy pilots chased the "Tic Tac" off California, a pair of Air Force reservists in a humble trainer plane spent about eighteen minutes trying to catch something over the capital's back yard. They never did. Seventy-eight years ago tonight, on November 18, 1948, a glowing, wingless oval toyed with them above Andrews Air Force Base in Camp Springs, Maryland, a few miles from the U.S. Capitol.

The case ended up in the Air Force's UFO files (Project Sign, later folded into Project Blue Book) as Incident 207, and the pilots' signed statements are still there to read. That's what makes it so fun: we don't have to guess what the witnesses said. We have their words.

A light that wouldn't behave

It was a Thursday night, and the base's 2238th Air Force Reserve Training Center had pilots up for night proficiency flying. The weather, according to the official report, was about as good as it gets: "CAVU, no smoke, haze or fog. Full moon."

At roughly 9:45 p.m., 2nd Lt. Kenwood W. Jackson spotted "a lighted object flying from northeast to southwest across Andrews Field." He and 2nd Lt. Henry G. Combs were flying a T-6 Texan, the classic two-seat trainer. Combs' first thought was the sensible one: probably just an airplane with burned-out navigation lights. So he went to take a look.

"As I came in," Combs wrote, "the object took evasive action."

The chase

What followed reads like a dogfight in which only one side knew the rules. Combs switched off his own wing and tail lights and tried to keep his exhaust flame hidden so he could sneak up on the thing. It kept "going quickly up and over my aircraft." He tried to line it up against the lights of Washington, D.C., and the moon to silhouette it, flying "very, very tight 360 degree turns with flaps down." And here's the line that gives today's post its title:

"The object could turn inside of my aircraft even under the preceding condition mentioned."

Combs also noted "the very quick variation of air speed from approximately 80 MPH up to 500 or 600 MPH." All he could make out was "an oblong ball, with one light, no wings and no exhaust flame."

Jackson's statement describes the same cat-and-mouse game. While they dove at it at about 240 mph, the object "would climb vertically then drop below us from behind and continue to circle."

Lights on

Finally, at about 7,500 feet, Combs pulled up sharply, came in underneath the object at an estimated 300 to 400 feet, and hit it with his landing light. It had, he said, "a very dull gray glow to it and was oblong in shape." Jackson saw the same thing: "It appeared to be oval, no wings, no tail surfaces."

Then it left. According to Jackson, it "headed to the Northeast climbing rapidly," and they lost sight of it around 8,000 feet at 10:03 p.m. Combs said it made "a very tight turn and headed for the east coast at about 500 to 600 MPH."

The witnesses on the ground (and in the pattern)

A second reserve pilot, flying in the local traffic pattern at 1,000 feet, signed a statement saying he saw "the same object" pass directly overhead across the northeast corner of the field. The Debrief identifies him as 2nd Lt. Glen L. Stalker.

On the ground, a staff sergeant named John Kushner (the typed transcript spells it "Kushmer") was standing by a parked plane when he heard a noise and saw "a shining object coming across the sky." It "sounded like a P-47 only twice as loud," he wrote, "but it couldn't have been a P-47 and I did not see any exhaust." When the pilots landed, some of them asked him if he'd seen anything. "This object did not look like an aircraft."

The base's report to Air Force intelligence, filed under the wonderfully blunt subject line "Flying Discs," summed it up: the object was "highly maneuverable, seemed aware of the presence of following aircraft, and capable of almost vertical flight," smaller than a T-6, oval or ovate. The witnesses were considered reliable.

So... a balloon?

This is where the file gets entertaining. According to The Debrief's review of the records, one analyst at Air Materiel Command at Wright-Patterson floated the idea of a weather balloon and suggested it would be "an interesting experiment" to have a plane chase a balloon and see whether it seemed to perform "evasive maneuvers." Another reviewer reportedly wrote a single sentence on the next page: "Definitely not a weather balloon."

There are some loose ends worth admitting. The investigators weren't even sure whether the pilots had been in one plane or two, and The Debrief's writer suggests the "twice as loud as a P-47" roar Kushner heard might have been a real P-47 in the air that night. That one is speculation, not something the file confirms. And nobody had radar, photos, or sketches; the report says plainly, "No photographs available."

Here's the fun "what if," clearly labeled as such: if a balloon really did all this, it was the most athletic balloon in Air Force history, one that outclimbed a diving trainer, slipped behind it, and then left at hundreds of miles an hour. If it wasn't a balloon, then something oval and wingless spent a quiet November evening in 1948 running laps around one of the most important airfields in America, and nobody ever found out what it was.

Seventy-eight years later, it's still listed in many case catalogs as unexplained. Look up tonight. Just in case.

Sources: Project Blue Book/Project Sign records for Incident 207 (Andrews AFB, Nov. 18, 1948), transcribed by NICAP (nicap.org); Jazz Shaw, "Incident 207: A Tic Tac over Washington, DC, in 1948?", The Debrief.

Tuesday, November 17, 2026

Spy Agency Goes Dark: NSA's Classified NSANet Network Hit by Outage After "Routine Maintenance"


 

The week of breakdowns has now reached America's most secretive spy agency. On Tuesday, Nov. 17, 2026, NSANet, the highly classified network the National Security Agency uses for its internal communications, went down. CNN broke the story, citing six people familiar with the matter. Workers at the agency's Fort Meade, Maryland, headquarters were told to stagger their arrivals while the problem was assessed.

As of 6:30 p.m. Arizona time (MST), Tuesday, Nov. 17. This is a developing story. Neither the NSA nor any outlet we checked has confirmed that NSANet is fully restored.

What went down

NSANet lets NSA employees send and receive classified information internally, including top-secret material. CNN posted the news on X just after 8:30 a.m. Arizona time. According to the Associated Press, a defense official who spoke on condition of anonymity confirmed that the problem disrupted NSANet operations.

via @CNN on X

The network wasn't completely dead. One source told The Record it was "only providing intermittent service." The staggered arrivals, the source said, were meant to avoid tens of thousands of employees all signing on to the network at the same time. CBS News reported that sources called this "Code Gray," a modified reporting schedule. CNN, citing a New York Times report, described an employee voicemail recording that called the situation a "code yellow" and told non-emergency staff to come in on a staggered schedule. CBS also reported that some activities were moved to other NSA facilities around the country.

The NSA's explanation: maintenance

On Tuesday afternoon the agency released a short statement: "The National Security Agency experienced temporary degradation during scheduled routine maintenance. While some internal systems were affected, mission-critical capabilities remain fully operational and our ability to defend national security continues." It added that NSA infrastructure "is designed with multiple layers of redundancy." As The Guardian noted, the statement did not name the network or say what caused the problem, how long it lasted or whether service had been fully restored.

Later in the afternoon, Director of National Intelligence Jay Clayton went further. CNN reported that he blamed the outage on software patches for major vulnerabilities discovered last month. "The patching that has gone on following that has caused some of these systems to not come back up when you patch them as expected," Clayton said on Fox Business. "That is that is what has happened at the NSA today." According to CNN, those vulnerabilities are in PHP, a widely used programming language for websites. Two sources also told CBS News that the outage came from routine system patching, though CBS said "the precise circumstances surrounding the disruption remain unclear."

via @BNONews on X

A hack? Officials say no

Every outlet we checked reported that there's no sign of a cyberattack. NBC News quoted Clayton: "This is not a cyber attack, and this is not a coordinated effort by a nation state. We've looked very closely." NBC also reported no sign that the outage affected the NSA's work. A former senior NSA official told CNN that NSANet is "more of a network of networks," and called the outage "alarming, but likely not crippling." CNN's sources said the Five Eyes intelligence-sharing system was not affected, and that the government has backup channels for reaching President Trump, who is traveling in Asia.

Not everyone is reassured. Former Defense Department analyst Mike Wiacek told The Guardian that "four major outages in under a week" look "suspiciously" like what he'd expect an attack to look like. He also said, "You can't compress months of forensic work into a few hours."

via @NBCNews on X

Is it fixed?

Not confirmed. A source told CNN that restoring the network was "ongoing but not yet complete." CNN reported that sometime Tuesday evening, the employee line switched to "code green" and told staff to report as scheduled. CNN added, though, that it "was not immediately clear whether the outage was resolved." An NBC News analysis said the network "stopped working for several hours." The NSA hasn't said when the trouble started or ended, and it hasn't said exactly which patch or system failed.

Six outages in six days

Politico counted "6 major outages in 6 days." The run has included last week's Microsoft Outlook outage, Friday's FAA ground stop that The Record said was traced to a single router in Arkansas, Monday's Chase banking outage and United Airlines tech outage, and Tuesday morning's Apple outage. The Record said there is "no evidence that they are linked." According to a separate Politico report, lawmakers are calling for an investigation into the string of outages.

The agency that listens to the world couldn't count on its own internal network for part of Tuesday. We'll update this post if the NSA confirms what happened.

Signed Out and Stuck at Checkout: Apple Outage Knocks Out iCloud, Apple Pay and the App Store


The run of big tech breakdowns isn't over yet. On Tuesday, Nov. 17, 2026, Apple users across the U.S. suddenly found themselves signed out of iCloud and unable to get back in. Apple Pay, the App Store, Apple Music and Apple Support were hit too. Apple's own status pages now confirm problems with several of its services, and the company says it's working on a fix.

As of 11:15 a.m. Arizona time (MST), Tuesday, Nov. 17. This is a developing story. Apple has not said what caused the outage, and it has not announced that service is restored.

Signed out and locked out

Trouble reports began piling up on the outage tracker Downdetector late Tuesday morning Eastern time. According to USA Today, Apple Pay reports began to spike around 11:40 a.m. Eastern (9:40 a.m. Arizona time), and iCloud reports surged just before noon Eastern. Downdetector's own alerts on X put the start of the Apple Support problems at 11:45 a.m. Eastern and Apple Pay at 11:48 a.m. Eastern. Tom's Guide said Apple Pay reports jumped to 2,000 "in a matter of minutes."

via @downdetector on X

9to5Mac reported that people were being unexpectedly signed out of iCloud on their iPhones and Macs, then hitting verification failures or "unknown errors" when they tried to sign back in. Others said the App Store wouldn't load or download apps, and that Apple Music and new-device activation were failing. Developers said they couldn't get into App Store Connect. MacRumors summed it up: "Anything related to an Apple Account seems to be malfunctioning, with users unable to sign in." It also noted social media reports of trouble at Apple retail stores.

The New York Post quoted one Downdetector user who posted the error message they kept seeing: "Failed to verify your identity. Try again." Another complained, "Can't activate devices or log into Apple Business." The Post said complaints also came from users in Brazil, Greece and Latvia.

via @disclosetv on X

What Apple is saying

Apple hasn't put out a public statement. USA Today and Fox News both said Apple didn't respond to their requests for comment. Apple's status pages, though, now tell the story. Early reports from 9to5Mac noted the Apple System Status page was still showing services as available. As of our last check, it lists "iCloud Account & Sign In" as having an issue that affects all users, warning that the service "may be slow or unavailable." It also shows outages for the App Store and Apple Music, and says AppleCare purchases on devices are "temporarily unavailable." Apple's page dates the iCloud, App Store and Apple Music problems to 8:45 a.m. Pacific (9:45 a.m. Arizona time). Apple Pay was still listed as available, even though users kept reporting trouble with it.

On Apple's developer status page, Account, App Store Connect, the Apple Music API and Apple Podcasts Connect are all marked as outages. Apple's message there reads: "Users are experiencing a problem with this service. We are working to resolve this issue."

via @WatcherGuru on X

What we still don't know

Apple hasn't said what broke, how many people were affected or when everything will be back. The New York Post reported that the cause and the timetable for restoring service "remained unclear." We have seen no report tying the outage to a cyberattack, and Apple hasn't addressed that question.

Gmail and Marriott too?

Social media posts on Tuesday lumped the Apple trouble together with Gmail, Marriott and Microsoft Outlook. Fox News did report a rise in Downdetector complaints about Gmail sending and receiving over the past 24 hours, but Google's Workspace Status Dashboard showed no active disruptions. Fox also reported that Marriott customers had trouble logging into the hotel chain's app and website Tuesday morning. Gulf News said those reports began around 9:17 a.m. Eastern. Marriott did not respond to Fox News. We found no major outlet confirming a new Outlook outage on Tuesday, and nothing links any of these problems to Apple's.

A brutal week for the systems we depend on

As USA Today pointed out, Apple's outage follows Monday's Chase banking outage, which spilled over to Wells Fargo, Bank of America, Zelle and others. It also follows last week's Microsoft outage that knocked out Outlook and other Microsoft 365 apps, and the FAA communications failure that grounded flights nationwide. The New York Post added Monday's United Airlines tech outage to the list. The Post said there was no established connection between any of those incidents and Tuesday's Apple problems.

Locked out of your Apple Account? Keep an eye on Apple's System Status page for updates. Carrying a backup card or a little cash wouldn't hurt either.

"Lift Her Up Quick!" 130 Years Since a Talking Airship Sailed Over Sacramento


 

Picture Sacramento on a cloudy Tuesday evening: November 17, 1896. No airplanes. No radio. The Wright brothers are still seven years away from Kitty Hawk. Streetcar men are finishing their shifts, people are out on the sidewalks, and then somebody looks up.

Something bright is drifting over the rooftops. And according to the newspapers the next day, it's talking.

Exactly 130 years ago tonight, Sacramento kicked off what historians now call the Great Airship Wave of 1896–1897. You could call it America's first big UFO flap, more than fifty years before anyone said "flying saucer."

A light that dodged the steeples

On November 18, 1896, the Sacramento Bee wrote that between 6 and 7 o'clock the night before, people on the sidewalks saw something coming over the housetops that looked like "merely an electric arc lamp propelled by some mysterious force." It came out of the east and moved unevenly toward the southwest, "dropping now nearer the Earth, and now suddenly rising into the air again."

That part, the Bee said, "hundreds of the people saw." The next part is where it gets strange.

Witnesses along a rough line across the city, many of them far apart, said they heard voices coming from the light. And not ghostly moans either, but, in the Bee's words, "the intelligible words and merry laughter of humans." When the light dipped too low, one voice supposedly called out: "Lift her up quick! You are making directly for that steeple!" Then the light climbed and carried on, roughly along the line of K Street.

The streetcar men speak up

The Bee's best witnesses came from the city's electric streetcar company. Charles Lusk, the company cashier, said he stepped outside his home at Twenty-Fourth and O Streets and saw the light. The next morning he told some of the carmen, and they said they'd seen it too near East Park. They also said they heard music and voices, including one that said: "Well, we ought to get to San Francisco by tomorrow noon."

G.C. Snyder, foreman of the car house, told the paper: "I assure you there is no joke about this matter, so far as I am concerned." He said he saw a white light around Twenty-Seventh and P Streets at about ten minutes to 7, rising, falling and swaying "as if it were being propelled by some motor power." He was sure it wasn't a star or a meteor. He also doubted it was a balloon, because he said it was moving toward the southwest while a heavy wind blew from that direction.

"Strange Craft of the Sky"

By November 19, the story was front-page news in the San Francisco Call under the headline "Strange Craft of the Sky." The Call's man in Sacramento said he had interviewed "scores of reputable citizens," and that many of them lived a mile or two apart but told matching stories.

From those accounts, the Call described a craft that was "oblong and egg-shaped, with fan-like wheels on either side." A man named R.L. Lowry gave one of the main descriptions. J.H. Vogel said the vessel was egg-shaped and he heard the people aboard, but it rose too fast to make out the words. E. Wenzel, who worked at a local brewery, said that when it passed over him the people on board were singing "a merry chorus." And a horse trainer at Agricultural Park (the Call spelled his name David Carl, the Bee wrote Curl) said he heard someone say, "We are too low down here; send her up higher."

The Call also said the "searchlight" stayed visible for more than thirty minutes, slowly fading as it headed southwest toward San Francisco.

Enter the mysterious inventor

You'd think a talking airship would be enough. But the story got bigger. The night before the sighting, the Bee had printed a telegram from New York saying a man had built an airship and planned to fly it to California in two days. The Bee itself thought that was an unlikely explanation.

Then the light was reported again on November 21, this time over Folsom, San Francisco, Oakland and other towns. Soon a San Francisco lawyer, George D. Collins, told reporters that a wealthy client had built a working airship. The papers loved it. But the inventor never appeared, Collins backed off under ridicule, and by December the California sightings had faded. The next spring, an even bigger airship wave rolled across the Midwest.

So what was it?

Here's the honest answer: nobody knows for sure. Historians usually point to a mix of things: balloons or kites carrying lanterns, bright stars or planets seen through broken clouds, practical jokers, and newspapers of the 1890s that liked a sensational story. No one in the U.S. had a working long-distance airship in 1896, and the "inventor" was never found.

Even the Bee couldn't decide. Its headline offered readers "aerial ship, ghost story, or meteor - as you like." One rival write-up joked that maybe it was "a stray meteor hunting for the rest of the gang."

Just for fun, a little speculation: it's interesting that people in 1896 saw what they expected to see in 1896, a man-made machine with a searchlight, wheels and a crew who spoke plain English. Seventy years later, people saw silver saucers. Today, it's orbs, triangles and drones. Is the sky changing, or are we? That's a question, not a claim, but it's what makes Sacramento's talking light worth remembering 130 years later.

So tonight around 6 o'clock, step outside and look east. If something bright drifts by and tells you to mind the steeple... well, you know who to call.

Sources: Sacramento Bee, Nov. 18, 1896, and San Francisco Call, Nov. 19, 1896 ("Strange Craft of the Sky," via Library of Congress Chronicling America); newspaper transcriptions at Patrick Gross's airship archive; background from UFO Decoder.

Monday, November 16, 2026

Grounded at the Gate: United Airlines System Outage Delays Departures, Days After FAA Ground Stop


Just three days after the FAA froze every departure in the country, air travelers got another jolt on Monday. A computer outage at United Airlines left planes waiting at gates across the U.S. on the afternoon of Nov. 16, 2026, because pilots couldn't get the final weight numbers they need before takeoff. United says the problem is now fixed and that there's no sign of a cyberattack.

As of 6:15 p.m. Arizona time (MST), Monday, Nov. 16. United says the issue has been resolved. The airline has not said what caused the outage.

"A widespread system outage"

United first confirmed the trouble a little before 3 p.m. Arizona time (just before 5 p.m. Eastern), CNN reported. Replying to a customer on X, the airline wrote: "We're aware of the widespread system outage, and our teams are working hard to get things back up and running as soon as possible." The Associated Press sent the news to its 16.5 million followers at 3:20 p.m. Arizona time:

via @AP on X

United said flights already in the air weren't affected, and neither were its regional United Express flights. The FAA said the problem was on United's end. "It's not an FAA equipment issue," the agency said, according to CNN.

Pilots told: don't log out

The outage hit the tools flight crews use to get a plane ready to go. CNN obtained an internal company alert telling pilots not to log out of several systems, because they might not be able to sign back in. Flight planning, weather briefing and crew management tools were all affected. The memo didn't say what caused the outage.

The Air Line Pilots Association told members the outage was "affecting multiple pilot facing applications" and that United could not "provide outbound flights with final weights," according to CNBC. Reuters, in a report carried by The Post and Courier, explained that pilots need that weight information for their pre-departure calculations.

Air traffic control audio published by CNN caught the moment it hit. "Hey, we're uh, still waiting on our final weights," the pilot of United Flight 1728, headed from El Paso to Denver, told a controller. "We just contacted ops and apparently there's a company-wide system outage on it so might be a while."

Fox News reported that at least one plane went back to the gate because the crew couldn't get critical performance data:

via @FoxNews on X

How many flights were delayed?

That depends on who's counting. United spokesperson Leslie Scott told CNN the outage lasted about 30 minutes and affected fewer than 150 flights. The flight-tracking site FlightAware showed 418 United flights delayed late Monday afternoon. That's 13 percent of the airline's schedule as of 5:30 p.m., according to Reuters, and DW reported the same number. But Reuters pointed out that FlightAware's count doesn't show how many of those delays the outage actually caused.

United: "The issue has been resolved"

Flightradar24 said on X at 3:28 p.m. Arizona time that it was seeing United mainline departures start up again. CNN reported that United announced the fix about an hour after first acknowledging the problem. "We have resolved a technology issue that delayed flight departures," the airline said in a statement. "While some flights were delayed, there was no impact on flights in progress, or on United Express flights." United posted the all-clear at 4:13 p.m. Arizona time:

via @united on X

"There is no indication that this is a cybersecurity-related issue," United said. CNBC and Reuters both reported that there's no sign the outage had anything to do with Friday's FAA shutdown. Still unknown: what actually broke. United hasn't said, and the FAA didn't immediately respond to Reuters' request for comment. The AP's latest headline also says United resolved the problem.

A rough week for the systems we depend on

The industry had mostly gotten back to normal after Friday's nationwide ground stop, which was lifted just after 8 p.m. Eastern. Reuters said that stop lasted nearly five hours. Transportation Secretary Sean Duffy blamed it on a router in Arkansas that overwhelmed systems feeding radar and other data to air traffic control, CNBC reported. CNN reported that contractor L3Harris had been doing routine work switching old copper telecom lines to fiber.

The United outage also came on the same day as the Chase software bug that locked customers out of their banking apps, and just days after Microsoft's Outlook and Teams went down, as DW pointed out. None of these breakdowns has been tied to a cyberattack.

Flying United soon? The airline says to check the latest status of your flight on its website or in the United app.

Cigar in the Sky Over Mexico: UFO, or Was It Starship Flight 15?

On the evening of Friday, November 13, phones across Mexico and Central America started pointing at the same strange thing: a long, glowing, cigar-shaped object with lights trailing behind it, sliding across the sky somewhere around 7 to 8 p.m. local time. This video stitches together several of those clips, and the host slows them down, brightens them, and argues the object is too slow and too low to be a SpaceX rocket.

Here's the catch: Honduras's civil aviation agency (AHAC) said the next day that the bright object seen over the country was SpaceX's Starship launch from Boca Chica, Texas (Flight 15 lifted off that same day), and that its path had been covered by an FAA notice. None of the clips here has been independently verified, so treat this as a fun side-by-side and decide for yourself: alien cigar, or a very big rocket putting on a show?

Video: "MYSTERIOUS UFO Filmed Over Multiple Countries! What's Going On?!" by UFO Phenomena on YouTube.