Tuesday, November 17, 2026

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.

Saturday, November 14, 2026

Shelter in Place: Mystery Drones Send U.S. Airmen Running for Cover at RAF Lakenheath

Something buzzed the skies over RAF Lakenheath in Suffolk, England, on the evening of Friday, November 13, 2026, and it was enough to get American personnel at the base told to "shelter in place." In this Sky News report, defence and security editor Deborah Haynes walks through the alert Sky News obtained, as the U.S. Air Force responded to what it calls "suspected unauthorised drone activity."

Officials say no personnel, aircraft, or infrastructure were affected and the situation has been "resolved," but nobody has said who (or what) was flying, where it came from, or why. If the name Lakenheath rings a bell, it should: the same base was at the center of a run of mystery drone sightings back in November 2024. Drones, spies, or something stranger? For now it's officially unexplained, so watch and decide for yourself.

Video: "US military responds to 'suspected unauthorised drone activity' at UK air base" by Sky News on YouTube.

The Jellyfish Over Anchorage: Alaska's Tentacled UFO, and the Kite Theory That Won't Go Away


 

Picture it: a June evening in Anchorage, the sky still bright after 10 p.m. the way only an Alaskan summer can manage, and a rainbow stretched across the horizon. You roll down the car window to grab a few photos. Then something dark drifts into the frame, hanging right there in the rainbow, trailing long, wriggling tentacles.

That's the story Sara Jane Osborn told the Daily Mail this week, and her footage of a so-called "jellyfish UFO" has been floating around the internet ever since. It's a great story. It's also a perfect case study in how a strange shape in the sky can go from "WHAT IS IT?!" to "probably a kite" in about five days.

A rainbow, a parking lot, and "is that a mosquito?"

According to the Daily Mail's November 10 interview, Osborn and her husband, Pete, were in Anchorage on business on June 15, 2026. Around 10:13 p.m., while they drove along Sixth Avenue, she started photographing a rainbow. Pete pulled into an empty downtown parking lot so she could shoot without traffic lights in the way.

Then she noticed a speck she first wrote off as a bug. "I was annoyed, because I was like, is that a mosquito?" she recalled. When she looked past her phone screen, the shape was still there: dark, "black and silver," with dangling appendages that seemed to move independently as it hovered and turned side to side. She took a burst of stills and started recording.

The object hung above distant trees in the direction of Joint Base Elmendorf-Richardson (JBER), home to F-22 Raptors. Osborn said it stayed visible for about three minutes, then "disappeared almost as quickly as it came."

The search for a kite flyer

Here's the part that makes the Osborns' account interesting. They didn't just shrug and drive off. They went to a nearby park hoping to catch someone reeling in a kite. "And there was nobody taking down a kite," Osborn said. They drove toward Arctic Valley and scanned the treeline for about 30 minutes. Nothing.

Osborn, who lived in Anchorage for years, said she knows the city's colorful kites, and this didn't look or move like one. "It was very clearly not a kite in its movements," she said. Asked who might know what it really was, she gave the line that made headlines: "Only God and the government." To her credit, she also floated a down-to-earth possibility herself: "maybe it's a drone-type thing."

Five months later, it goes viral

Here's a twist many headlines skipped: this isn't a new sighting. Alaska News reports that Osborn posted the 57-second clip to Facebook just after 10 p.m. on June 15, and it has since picked up about 168,000 views. It only went global in November, once the Daily Mail story hit.

And once it went global, the analysts showed up.

What the experts say

On NewsNation's "Jesse Weber Live," "UFO Witness" host Ben Hansen said he believes Osborn's images are legitimate, captured "in camera" and not faked. But he and former UAP Task Force analyst Sarah Gamm both leaned toward an ordinary explanation. "Our likely suspect right now is perhaps some sort of kite, kite-ish, balloon type thing," Hansen said, adding that military exercises with high-altitude balloon launches were happening in the region around that time. Gamm's verdict: "Officially, I would call it unidentified, but most likely (it's) a high-altitude balloon."

Kite fans on Reddit and the analysis forum Metabunk went further. They pointed to octopus show kites, big soft kites sold online in lengths of up to about 100 feet, mostly long fabric tentacles that flutter out of step with each other, just like the "independently moving" arms in the video. Alaska News checked the weather: shortly before 10 p.m., airport stations recorded west winds of 8 to 11 knots, decent kite weather, easing to 4 knots at Merrill Field an hour later. The object also seems to bob around one spot rather than cross the sky, which is what a tethered kite does.

Even Jeremy Corbell, the filmmaker who released the famous 2018 Iraq "jellyfish" UAP video, reportedly said on his Weaponized program on November 11 that this one was most likely a tethered octopus-style kite. When the guy behind the most famous jellyfish UFO calls kite, that's saying something.

Was it really "over" the base?

Probably not. The video was shot toward JBER, but that doesn't put the object above it. Metabunk contributors who mapped the viewpoint estimated the nearest part of the base was about 4 km away and not even in the frame. And as the Daily Mail itself noted, without knowing how far away the object was, its apparent size tells us nothing reliable about how big it actually was.

So... case closed?

Not officially. Nobody has come forward with the kite, no one has matched it to a specific balloon launch, and a phone video can't measure distance. The Osborns' empty-park search is the main reason some people still doubt the kite theory, though a show kite can fly on a long line, with its owner out of sight behind trees or buildings.

Here's my fun "what if," and it's pure speculation: imagine whoever was holding that string, somewhere out of sight in East Anchorage, scrolling past headlines about a giant alien jellyfish menacing an F-22 base. If that's you, the internet would love to hear from you.

What we don't have is any evidence of anything exotic: no radar track, no military statement, nothing in the footage a kite in a breeze couldn't do. Still, it's a great reminder that strange shapes are often the easiest to solve, because somebody usually makes a product that looks exactly like them. If you ever catch something odd on camera, write down the time, direction, and wind, and look around for anyone holding a string.

What do you think: octopus kite, high-altitude balloon, or something stranger? Tell me in the comments.

Sources: Daily Mail (Nov. 10, 2026, interview with Sara Jane Osborn); NewsNation, "Tentacle UFO caught on video in Alaska likely a weather balloon: Experts"; Alaska News, "Anchorage's viral 'jellyfish UFO' was filmed in June, and it may be a kite"; Track The Unknown.

Friday, November 13, 2026

Nationwide Ground Stop: FAA Freezes Every U.S. Departure After Air Traffic Control Communications Failure

Update, 6:50 p.m. Arizona time (MST), Nov. 13: Ground stop lifted

The FAA has lifted the nationwide ground stop, and departures can resume. ABC News reported at 6:23 p.m. Arizona time that the FAA said the stop was over, and Flightradar24 confirmed the lift minutes later. The stop began at 1:54 p.m. Arizona time and lasted more than four hours, ending well before the 9 p.m. Arizona time estimate on the FAA's advisory. The FAA's live airport status page no longer lists a nationwide ground stop, only normal local delays.

The fallout is huge. ABC News reports nearly 5,000 flights were canceled. United and JetBlue said they would cancel most of their remaining flights Friday night, except for some international flights. Air Canada canceled all its remaining Canada-U.S. flights for the night. Delta and United are waiving change fees for affected travelers, according to the AP. Experts quoted by the BBC called it the longest U.S. air traffic grounding since 9/11. During the stop, some departures were cleared over the ocean, in Alaska and Hawaii, and on some international routes.

At a White House briefing, Homeland Security Secretary Markwayne Mullin blamed a "telecommunications outage" and said there was "no cyberattack." He also said "the public was never at danger." There is no sign it was linked to Thursday's Microsoft 365 outage. According to Flightradar24, Secretary Duffy said switches and routers became overloaded and shut down after they began providing inconsistent data. Sources told CBS News that an update to the private air traffic control communications network, which CBS says L3Harris operates, made the network reboot and then crash. L3Harris hadn't commented as of the BBC's report, and the FAA hasn't released a full official explanation.

Flightradar24 warned that "it will take a long time for traffic to return to normal levels," and JetBlue said it expects more disruptions and cancellations Saturday. If you're flying this weekend, check your airline's app before you head to the airport.

Air travel across the United States came to a sudden halt Friday afternoon. The Federal Aviation Administration ordered an extremely rare nationwide ground stop at every U.S. airport on Nov. 13, 2026, "due to extraordinary circumstances and for reasons of safety." The cause, according to the FAA and Transportation Secretary Sean Duffy, was a communication problem hitting the air traffic control centers that guide planes across the country.

Originally published at 2:45 p.m. Arizona time (MST), Friday, Nov. 13. Updated at 6:50 p.m. Arizona time: the ground stop has been lifted (see the update above).

Departures frozen coast to coast

An advisory from the FAA's Air Traffic Control System Command Center put the ground stop into effect at 2:54 p.m. Central time, which is 1:54 p.m. Arizona time. Its message was blunt: "All departing traffic should remain ground stopped until further notice." Planes already in the air were allowed to keep flying and land. The FAA said inbound international flights would be "managed on a case by case basis."

Flight tracker Flightradar24 broke the news to millions of followers within minutes:

via @flightradar24 on X

That post has been viewed more than 1.1 million times. A few minutes later, Flightradar24 said about 3,100 aircraft were in the air headed for U.S. airports, and that "no additional aircraft are taking off at this time."

What went wrong?

Secretary Duffy confirmed the stop on X and pointed to a communications failure at the centers that manage high-altitude traffic between airports:

via @SecDuffy on X

The FAA's own statement was a little narrower. It said the problem hit "multiple" Air Route Traffic Control Centers, while Duffy said "all" of them. Charlotte Douglas International Airport told WBTV the stop was tied to "an FAA equipment outage." American Airlines told customers on X that the FAA was "working to resolve a technical issue affecting telecommunications at many air traffic control facilities across the country."

At first, officials didn't explain what actually failed. Some accounts on X speculated about a cyberattack, but Homeland Security Secretary Markwayne Mullin later said there was "no cyberattack" and blamed a telecommunications outage. Early explanations of the technical cause are in the update at the top of this post. The FAA hasn't released a full official explanation yet.

The Associated Press summed up the situation for its 16 million followers:

via @AP on X

Only the second time since 9/11

Nationwide ground stops almost never happen. The last one came on Jan. 11, 2023, when the FAA's NOTAM pilot-alert system failed. Departures were paused for about 90 minutes, and the ripple effects caused more than 10,000 delays and over 1,300 cancellations. Before that, the whole U.S. airspace was cleared after the Sept. 11, 2001, attacks.

Where things stand now

As of 6:50 p.m. Arizona time (MST), Friday, Nov. 13. The FAA has lifted the nationwide ground stop, and departures are allowed to resume. ABC News reported the FAA's announcement at 6:23 p.m. Arizona time, after a stop of more than four hours. That was well before the 9 p.m. Arizona time estimate on the original advisory. The FAA's live airport status page no longer shows a nationwide ground stop, only normal local delays like wind-related ground delay programs at San Francisco and LaGuardia.

Earlier in the afternoon, a passenger at LAX told CBS News that newly landed planes couldn't get to their gates because departing jets were stuck in place. With nearly 5,000 flights canceled, airlines expect the disruption to spill into Saturday.

If you're flying tonight or this weekend, check your airline's app before heading to the airport, look for change-fee waivers, and expect delays and cancellations to keep rippling through the schedule.

We'll keep updating this story as the FAA shares more.

Sources

'Good Luck With the Aliens': The Silver Canister That Hovered Off a Pilot's Wingtip Over Rhode Island



Picture a calm flight over Rhode Island. You're at about 3,500 feet in a small single-engine plane, the bay glittering below, nothing on the radio but routine chatter. Then you glance out the right window and something is sitting there. Not flying past. Sitting there. A little silver canister, apparently hanging in the air right off your wingtip.

That's the story one private pilot told air traffic controllers at Rhode Island T.F. Green International Airport, and the recording of that radio exchange has been making the rounds again this week. It's short, it's strange, and it comes with one of the best deadpan lines ever heard on an aviation frequency.

"A small silver canister. Do you know what that could be?"

According to the air traffic control audio, published by the aviation YouTube channel VASAviation and reported by Fox News and NewsNation, the pilot was flying a Piper PA-32RT-300T Turbo Lance II, a six-seat, single-engine propeller plane. He keyed the mic and told the controller:

"Looks like a strange, small object that we just floated by. A small silver canister. Do you know what that could be?"

He added that it "appears to be standing still." According to the reports, the object was near the plane's right wingtip, appeared to move alongside the aircraft for a while, and then was simply gone from view.

The controller did exactly what you'd hope a controller would do: checked for other traffic and asked the sensible question. There were no other reports of an object in the area, and ATC asked whether it might be a drone or a balloon.

The pilot's answer is the part that sticks with you:

"I saw nothing attached to it. It was sort of hovering there. It was astonishing. I don't know what it was."

"Good luck with the aliens"

Then the frequency did what aviation frequencies sometimes do when something odd happens: it got a little playful. One voice called the encounter "creepy." Another pilot listening in chimed in with "I want to believe him," a nod to the famous X-Files poster. And someone on the frequency signed off the moment with a line that has since become the headline of the whole story: "Good luck with the aliens."

It's funny, but it also says something about how pilot reports have traditionally been received. For decades, pilots who saw something odd often kept quiet because of the stigma. Here, the report went out on an open frequency, got logged, and got a laugh, but nobody told him he was crazy.

What we actually know, and what we don't

It's worth being careful here, because this one tends to get oversold. There is no photo or video of the object itself. What's circulating is the ATC audio, packaged by VASAviation in its usual style with map and radar graphics synced to the radio calls. So the "UFO video" headlines are really about a recording of a conversation about a UFO.

The exact date of the flight is also fuzzy. The recording was posted by VASAviation, and the coverage describes it as having surfaced and then resurfaced, but the reports don't agree on precisely when the flight happened. The controller also said there were no other reports in the area, and nothing in the coverage says the object was confirmed on radar.

When Fox News Digital asked the FAA about it, the agency gave its standard explanation: it documents UAP sightings whenever a pilot reports one to an air traffic control facility, and if supporting information such as radar data corroborates the report, the FAA shares it with the UAP Task Force. Whether that happened in this case hasn't been made public.

So what was it?

Here's where we put on our speculation hat, and we'll say so plainly. The boring answers are genuinely good ones. A mylar party balloon, a balloon carrying a small instrument package, a consumer drone, or a piece of shiny drifting debris could all look like a "silver canister," and at the speed even a small plane flies, judging whether something is truly stationary is harder than it sounds. A balloon drifting with the wind can look eerily motionless from a moving cockpit.

But the pilot's own description pushes back a little. He specifically said he saw nothing attached to it, and he described it as hovering and then moving alongside the plane. Small metallic cylinders show up again and again in modern reports, including in material the Pentagon's UAP office has released, which is part of why a story like this gets people's attention. That doesn't make it alien. It just makes it part of a pattern people want explained.

The real problem: one witness, no data

This little encounter is a perfect example of why the UAP debate keeps going in circles. One sincere witness, a few seconds of observation, no imagery, and no corroborating radar. You can't prove it was a balloon, and you can't prove it wasn't.

That's exactly the gap some scientists say they want to close. Just this week, Harvard astrophysicist Avi Loeb told NewsNation's "The Hill" that his team plans to assemble a prototype system at an Ithaca, New York, observatory that was once home to Carl Sagan, using radar to spot objects and then steering a meter-class telescope onto them to capture high-resolution images and a spectrum. As he put it, "You can actually resolve them and figure out what they are."

Until tools like that are watching the skies, cases like the Rhode Island silver canister will stay where they are now: a strange voice on the radio, a laugh from the controllers, and a pilot who honestly doesn't know what floated past his wing.

What do you think he saw? A runaway balloon, a drone, or something else? Let us know in the comments.

Sources: Fox News, NewsNation, ATC audio via VASAviation, and NewsNation on Avi Loeb's telescope plan.