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.

Locked Out of Your Bank? Chase Software Bug Triggers Nationwide Banking Outage


If your banking app greeted you with an error on Monday, you were far from alone. Thousands of customers at some of America's biggest banks reported trouble logging in, seeing their balances and moving money on Nov. 16, 2026. JPMorgan Chase now says the trouble started with a software bug in its own systems, and that it rippled out to other banks and to Zelle payments.

As of 3:15 p.m. Arizona time (MST), Monday, Nov. 16. This is a developing story. Chase has not yet announced that service is fully restored.

Banking apps go dark across the country

Complaints started piling up on the outage tracker Downdetector Monday morning. WIRED reported the problems appeared to begin around 9:30 a.m. Eastern (7:30 a.m. Arizona time) and peaked around 2 p.m. Eastern (noon here). According to CBS News, nearly 4,800 people had reported problems with Chase by 2 p.m. Eastern, the most of any bank.

Fox News pushed the alert to its nearly 30 million followers, and it quickly became one of the most-shared posts on the story:

via @FoxNews on X

That post has been viewed nearly 2 million times. Downdetector also showed complaints spiking at Bank of America, Wells Fargo, U.S. Bank, Capital One and Truist, CBS reported. Bank of America customers reported problems with ATMs as well as online and mobile banking. Wells Fargo customers had trouble signing in. Some Chase customers saw a message reading, "Some services aren't available. We're working on them. Please try back later."

The Associated Press flagged the problem to its 16.5 million followers at 1:54 p.m. Eastern (11:54 a.m. Arizona time):

via @AP on X

The frustration wasn't only online. A Chase customer in Texas told CBS News he couldn't deposit a check at a Dallas branch, and that a teller told another customer the "system was down" without saying more.

What Chase says went wrong

Chase pinned the blame on itself, and ruled out hackers. "JPMorganChase has experienced a temporary issue related to a software bug in on-premise hardware systems—there is no evidence this is cyber-related," spokesperson Pablo Rodriguez told WIRED. The bank said it was "taking longer than usual to service some customers," but that customers "still have access to their accounts and funds."

Chase also said this was "not a systemic issue." Instead, it told CNBC that "other banks may have been impacted by slowness in transactions only to the extent that they were a party to a transaction with us." In other words, if your bank was trying to send money to or receive money from Chase, it could get stuck. CNBC's Eamon Javers reported there was no indication of bad actors involved.

ABC News shared the bank's statement on X:

via @ABC on X

Zelle, Visa and Mastercard: "We're not down"

Lots of people reported problems with Zelle, but the payment network insists it is fine. "Zelle is not down. Zelle is operating as it should," a spokesperson told WIRED, adding that customers use Zelle through their banks, which hold their money. U.S. Bank said its systems were "not directly impacted," but warned that Zelle payments with other banks might be delayed. Capital One told CBS News it had not been affected. Mastercard and Visa both said their networks were operating normally.

When will it be fixed?

Chase told ABC News it is "working diligently to resolve this by the end of the day today." As of this writing, the bank has not announced an all-clear. Some customers began posting on X in the last hour that their Chase accounts were working again, but that isn't official confirmation. The AP said Chase was still working to bring banking services back online.

Three big breakdowns in five days

Monday's trouble capped a rough stretch for the systems we all depend on. Microsoft's Outlook and Teams went down worldwide last Thursday, and on Friday the FAA ordered a rare nationwide ground stop after an air traffic control communications failure. None of the three has been linked to a cyberattack. "Each one has an explanation that makes sense on its own, but they all point to a common theme: the complexity and fragility of the systems that we depend on every day," Mike Chapple, an IT expert at the University of Notre Dame, told CBS News.

Our advice for now: don't panic, and don't make the same payment twice. Chase says your money is safe and still in your account. If a transfer is stuck, give it time before trying again, and watch for scammers who may pose as "bank support" during the confusion.

Twice the Size of an Aircraft Carrier: 40 Years Since JAL Flight 1628 Met a 'Mothership' Over Alaska


 

Forty years ago this week, on the evening of November 17, 1986, a Japan Air Lines Boeing 747 cargo jet was cruising over the dark, frozen interior of Alaska with a hold full of French wine. Somewhere northeast of Fort Yukon, its captain looked out the window and saw lights that, by his account, had no business being there. What followed became one of the most argued-over pilot sightings of the 20th century, and four decades later it still splits believers and skeptics right down the middle.

"Flying parallel and then suddenly approached very close"

The flight was JAL 1628, a Paris-to-Tokyo cargo run with stops in Reykjavík and Anchorage. In the cockpit were three crew members: Captain Kenju Terauchi, a 47-year-old pilot with 29 years of flying behind him, his co-pilot, and a flight engineer. Shortly after 5 p.m. local time, at about 35,000 feet, Terauchi reported lights to the left of and below the plane.

"They were flying parallel and then suddenly approached very close," he later told United Press International. He described two smaller objects and, at one point, a far larger one. He called them "the two small ships and the mother ship."

The captain radioed Anchorage air traffic control. With permission, the crew descended 4,000 feet and flew a complete 360-degree turn to see whether their company would follow. According to Terauchi, it did. "They were still following us," he said. As the jet passed near Eielson Air Force Base, outside Fairbanks, he said he glimpsed the silhouette of the big one behind them: a walnut-shaped craft with bulges above and below a wide, flat brim. "It was a very big one," he told UPI, "two times bigger than an aircraft carrier."

What the radar saw (and didn't)

This is where the story gets its staying power. FAA flight control reports indicated the object stayed with Flight 1628 for at least 32 minutes, and the controller handling the jet reported a return on his scope as close as five miles away. When the story broke at the end of December 1986, headlines announced that the sighting had been confirmed by FAA and Air Force radar.

After the jet landed safely in Anchorage, FAA investigators interviewed the crew and concluded they were "normal, professional, rational, (and had) no drug or alcohol involvement." And Terauchi kept his sense of humor. Asked why UFOs would tail a cargo plane, he joked: "We were carrying Beaujolais, a very famous wine made in France. Maybe they want to drink it." Asked whether he had been nervous: "No, I am the captain. I cannot be nervous."

But the radar picture got murkier on review. The military returns were later dismissed as clutter, and the target on the FAA's screens was judged to be most likely a coincidental split image of the 747 itself. A United Airlines jet and an Air Force C-130 in the area reported seeing nothing unusual, visually or on radar.

Jupiter, Mars, and a "UFO repeater"

The skeptics' case was led by Philip J. Klass of Aviation Week & Space Technology, who pointed out that Jupiter and Mars sat low in the sky in the direction Terauchi was looking. Jupiter was only about 10 degrees above the horizon, low enough, Klass argued, to seem level with a jet at 35,000 feet. He also noted that the pilot's later accounts didn't always match what he said on the radio that night.

The FAA's own data package added another wrinkle: it described Terauchi as a "UFO repeater" who had reported other sightings before and after November 17. One of them, in January 1987 over the same general area, was chalked up to lights from small villages diffused by thin clouds of ice crystals. Skeptical writers like Robert Sheaffer and Brian Dunning have argued that the captain, however capable, was not an unbiased observer when it came to spaceships.

The FAA man who never let it go

On the other side stands John Callahan, who in the 1980s was division chief of the FAA's Accidents, Evaluations and Investigations Division in Washington. Speaking at the National Press Club in 2007, Callahan said the voice tapes and radar data were gathered up and he briefed officials on them. By his account, at the end of that meeting one of the CIA attendees declared that the event "never happened" and that the data was being confiscated. That part is Callahan's own story, and it has never been independently confirmed, but it has made JAL 1628 a fixture of every disclosure documentary since.

Callahan himself said he first suspected a stealth military aircraft, but ended up calling the evidence inconclusive. "The FAA has procedures that cover tracking unidentified aircraft violating another's airspace," he said, "but it has no procedures for UFOs."

Why it still matters

Forty years on, Alaska's skies are back in the UFO headlines with the "jellyfish" video filmed near Anchorage, and the same old questions are back with it: what did the witnesses actually see, what did the instruments really record, and who gets to decide? JAL 1628 is a reminder that even a calm, sober, professional crew and a radar blip don't automatically add up to an answer. Was it planets on the horizon, a radar glitch, and a pilot primed to see ships? Or something that a cargo jet full of Beaujolais happened to cross paths with over the Yukon? Pour yourself a glass and decide for yourself.

Sources: UPI Archives, "A veteran pilot whose UFO sighting was confirmed on..." (Dec. 31, 1986); Fairbanks Daily News-Miner, "Close encounter over Interior Alaska draws coverage on UFO show" (2011); Wikipedia, "Japan Air Lines Cargo Flight 1628 incident" (citing the AP, The New York Times, and Skeptical Inquirer).

Sunday, November 15, 2026

The See-Through Visitor of Wilsonville: A Bedroom Full of Light, a 12-Year-Old's Photo, and a Night of Strange Symptoms


 

Most UFO reports start with someone glancing up. This one starts with a mom on her back patio in Wilsonville, Oregon, watching something drop out of the sky like it had been shot.

It was a little after 8 p.m. on August 25, 2026. The witness, identified only as "S" in her report to the National UFO Reporting Center (NUFORC), later described it this way: "I noticed what looked like something I've never seen fall out of the sky. Almost like a bird was shot dead in the air and plummeted."

And then it got weirder. According to her report, the object "went from looking rectangular to a large ball, then a small ball in a matter of a blink," trailing what she called "a stream following behind it what looked like smoke? But not smoke." She shouted to her partner and daughter that something was falling out of the sky. They looked up in time to see only the trail.

On most nights, that would be the whole story. A strange streak, a shrug, everybody goes back inside.

9:14 p.m.: The Room Lights Up

About an hour later, at 9:14 p.m. by the family's account, their 12-year-old daughter came running downstairs, scared, saying her whole bedroom was flashing with bright lights. Her parents ran up to see for themselves.

What they say they found was "this big object floating still pointed directly towards our home." It hovered there for almost a minute, the report says, "and then just disappeared!"

Here's the part that makes this case stand out: the daughter grabbed a photo while it was happening. S filed her report with NUFORC that same night, at 10:40 p.m. Pacific, describing the thing as "silver in color with a distorted, see-through surface, two really big lights and no distinct shape." Her daughter, who saw it first and up close, said it looked like "see-through silver."

How big? That's where the details get dizzying. The daughter told investigators it looked as wide as three airplanes, with what seemed to be its nose tilted upward. The NUFORC report form lists an estimated size of about 400 to 500 feet wide, at an elevation angle of 52 degrees, heading east, at a closest distance of "3-5 miles away?" (question mark theirs). Estimated speed: "Flash lighting speed. No joke."

The Morning After

The story didn't end when the lights went out. S reported that after the sighting she felt nauseous and had balance issues, and that her daughter had intermittent headaches throughout the night. Both felt better the next day.

The report's checklist of characteristics reads like a greatest-hits album of classic UFO lore: lights on the object, an aura or haze around it, a trail, emitted beams, and "electrical or magnetic effects."

To be clear, nobody has shown that the object caused the symptoms. A frightening late-night scare, a racing heart, and a sleepless kid can all produce headaches and queasiness on their own. But it's the kind of detail that has appeared in close-encounter reports for decades, which is part of why this case grabbed attention when the Daily Mail and others picked it up in mid-November.

The Investigator Checks the Boxes

NUFORC investigator Keith Bickford interviewed S on August 29, four days after the sighting. Then he went looking for the boring explanations, which is exactly what a good investigator should do.

  • Drones? Bickford contacted two farmers with property in the area who both use drones day and night for crop care. Neither had drones anywhere close to the size described.
  • Police reports? Both the Clackamas County Sheriff's Office and the Wilsonville Police Department had no UAP or UFO reports for that evening.
  • Aircraft? FlightRadar24 showed nothing.

His conclusion: "I am classifying this as an anomalous sighting."

That's not NUFORC saying "aliens." It's NUFORC saying the obvious suspects didn't pan out with the information available.

So What Was It?

Let's play skeptic and believer for a minute, and be upfront that everything in this section is speculation.

On the skeptical side: a "distorted, see-through surface" with two big lights is a description that can fit a reflection. Photos taken through a window at night are notorious for ghosting room lights, phone flashes, or outside lights onto the glass, and those reflections can look like they're "floating" outside. A falling, glowing object with a smoky trail an hour earlier could be a meteor or a piece of reentering debris, totally unrelated to what showed up at the window. And estimating size and distance for a light in the dark sky is incredibly hard, which may explain the jump from "outside the window" to "3-5 miles away."

On the other side: three people say they saw something, the witness reported it within about 90 minutes, there's a photo, and the investigator who actually interviewed her didn't land on a mundane answer. The object reportedly sat still for nearly a minute and then vanished, which is not what a meteor does.

And here's a fun "what if" to chew on: if the first object really did "fall" and change shape, and the second really did hover with beams pointed at the house, were they the same thing coming back for a second look? Pure speculation, but you can see why the family hasn't stopped thinking about it.

Wilsonville is a quiet suburb south of Portland. On the night of August 25, at least one 12-year-old there learned that the sky doesn't always mind its own business.

What do you think lit up that bedroom? Reflection, drone, debris, or something genuinely unidentified? Tell me in the comments.

Sources: NUFORC Sighting 200460 (witness report and Keith Bickford's investigation) and the Daily Mail, November 12, 2026.