TorontoStartsBook a call

Silicon Scoop · Technology

United Airlines Outage and Chase Bug Hit Travel, Banking

Craig Major·November 17, 2026

United’s outage delayed flights, a Chase bug slowed payments, and a separate Optimizely cyberattack reached websites across 178 organizations.

United Airlines Outage and Chase Bug Hit Travel, Banking

Estimated reading time: 11 minutes

Key Takeaways

  • United Airlines' outage on November 16 delayed departing flights. The Associated Press reported it lasted more than 90 minutes, while CNN reported about 30 minutes, so the duration depends on the source.
  • United said flights already in the air and United Express regional flights were not affected. It also said there was no indication of a cybersecurity cause.
  • JPMorgan Chase said a software bug in an on-premise hardware system slowed some transactions. The bank said the problem was not cyber-related and that customers could still reach their accounts and funds.
  • Zelle payment delays showed up at other banks only where they dealt with Chase. US Bank said its own systems were not directly affected, and Zelle said its service was operating normally.
  • A separate attack on Optimizely’s website testing platform affected 188 scripts across 178 organizations, according to researchers at Report URI.
  • None of the retrieved sources gave a dollar cost for the United or Chase incident, so founders should plan from the pattern rather than a price tag.

Table of contents

United Airlines' outage on November 16 ran for more than 90 minutes, according to the Associated Press, and it delayed departing flights. CNN, as summarized in our research briefing, put the same event at about 30 minutes. Both numbers are on the record, and the gap between them is part of the story.

On the same day, JPMorgan Chase said a software bug slowed some customer transactions. United said there was no indication its problem was cybersecurity-related, and Chase said its issue was not a cyberattack.

In a separate incident on November 16, an attacker used Optimizely’s website testing platform to put malicious code on customer websites. The three stories show how failures and attacks can spread through the services businesses depend on.

That is what makes the day useful for founders and operators. A small technical failure can spread through payments, travel, customer support and revenue operations within minutes. Treat your core systems, and the outside systems you rely on, as a business continuity risk. This post covers what each company said, where the reports disagree, and what to do about it.


What Happened in the United Airlines Outage

United Airlines had a system outage on November 16 that delayed departing flights, according to the AP report on the United outage, November 16. AP reported that it lasted more than 90 minutes.

What United said

The same AP report carries three United statements:

  • Flights already in the air were not affected.
  • United Express regional flights were not affected.
  • There was no indication the issue was cybersecurity-related.

These are company statements, not findings from an independent investigation. That matters later when we look at the cause.

What passengers saw

A separate report from Nine (by Adam Vidler, November 16) described a "widespread outage" hitting United's weight check system. Nine says this grounded passengers and delayed flights. It quoted United as saying: "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."

Nine also cited FlightAware, a flight tracking site, which showed about 418 United flights delayed at one point. That figure is a snapshot at a single moment. It is not a total for the whole event.

Source: AP report on the United outage, November 16

The weight check system, quote and FlightAware figure come from Nine's report by Adam Vidler, November 16 (article link not supplied in the research).


Why Reports Disagree: 30 Minutes or More Than 90

The United airline outage was reported differently by different outlets. This is a good reminder to check the source behind any number.

The two versions

  • AP: the outage lasted more than 90 minutes.
  • CNN, as summarized in the research briefing: it lasted about 30 minutes and affected fewer than 150 flights.
  • FlightAware, via Nine: about 418 flights were delayed at one point.

We could not link the CNN report, so treat its figures as relayed secondhand.

Why the numbers may differ

The sources do not explain the gap, so any reason is a guess. Outlets may have started the clock at different moments. One might count when the system failed, another when delays showed up at airports. Delays can also keep spreading after a system comes back.

The safe reading is that the exact duration and the total number of affected flights are still source-dependent. The one thing the retrieved reports agree on is that the outage was resolved.

Why this matters to operators

Your own incident reports will face the same problem. Customers, staff and partners will each report a different start time and a different impact. Write down your own timeline while the event is happening, with a named person responsible for it.

Source: AP report on the United outage, November 16

The CNN figures come from the research briefing. The 418-flight figure comes from Nine's report by Adam Vidler, November 16.


Cut the Manual Work Before It Slows You Down

Flowgrammer.ca builds business automation that takes repeat tasks off your team's plate, such as follow-ups, data entry, reporting and handoffs between tools. That saves hours every week and lets you grow without hiring for every new process.

👉 Talk to Flowgrammer about automating your workflows


The JPMorgan Chase Software Bug in On-Premise Hardware

Banking had its own trouble on November 16. JPMorgan Chase said it had a temporary issue related to a software bug in an on-premise hardware system. "On-premise" means equipment the company runs itself, rather than in a cloud provider's data center. That detail comes from the AP report on the Chase outage (courant.com), November 16.

What Chase said

Chase said:

  • The cause was a software bug, not a cyberattack.
  • Customers could still access their accounts and funds.
  • Some customers were being served more slowly than usual.

Reuters reported the same message: the bug slowed transactions and was not cyber-related. Nine quoted a Chase spokesperson: "JPMorganChase has experienced a temporary issue related to a software bug. It is taking longer than usual to service some customers."

What customers reported

Nine said social media users reported transaction problems at physical Chase branches. These are user reports, and we have no independent count of how many branches or customers were affected.

The "not systemic" claim

The research briefing says Reuters reported that Chase called the issue not systemic. The Reuters page's supported claims in our research confirm the bug and the "not cyber-related" statement, but not that wording. We are treating "not systemic" as unverified here.

Why a "bug" is still a serious word

A bug is not a hack. But for a customer waiting on a payment, the difference is small. The cost is the same: delay, confusion and extra calls to support.

Source: AP report on the Chase outage (courant.com), November 16 and Reuters report on Downdetector bank outage reports, November 16

The branch reports and the spokesperson quote come from Nine's report by Adam Vidler, November 16.


Zelle Payment Delays: How One Bank's Problem Reached Others

The Chase bug did not stay inside Chase. Other banks felt it wherever money moved to or from Chase accounts.

What other banks reported

Nine reported that Bank of America, Wells Fargo and US Bank also reported issues. These were mostly tied to sending money through Zelle, a payment network that moves money between bank accounts, to Chase accounts.

The AP report adds the key limit. Other banks saw slowness only to the extent they were parties to transactions with JPMorgan Chase. That is a dependency problem, not a sign that each bank had its own failure.

What US Bank said

Reuters reported that US Bank said its systems were not directly impacted, but Zelle payments involving other institutions could be delayed. Nine quoted the bank in more detail:

> "US Bank systems are not directly impacted. However, clients attempting to send or receive Zelle payments with another financial institution may experience transaction delays."

What Zelle said

Per Nine, Zelle confirmed its service was operating normally and that it does not hold consumer funds. So the delays were reported at the bank-to-bank connection points, not as a Zelle network failure. These are company statements, and we have no independent audit of how many payments were delayed or for how long.

The lesson for payment-dependent businesses

If your customers pay through one bank or one rail, a problem at a partner can look like a problem at your company. Your checkout or invoice may work fine while money still fails to arrive.

Source: AP report on the Chase outage (courant.com), November 16 and Reuters report on Downdetector bank outage reports, November 16

The bank-by-bank detail, the US Bank quote and Zelle's statement come from Nine's report by Adam Vidler, November 16.


FAQ-Worthy Context: The FAA Ground Stop Aftermath

Many readers asked whether the United outage was linked to a recent nationwide grounding. The retrieved sources do not support a link.

What Nine reported

According to Nine's report, a United passenger said the pilot told them the issue was separate from a recent nationwide grounding. That grounding caused thousands of cancellations and delays. This is one passenger's account of what a pilot said, not an official finding.

The same report says the Federal Aviation Administration, which authorized the earlier mass shutdown, acknowledged the United outage but referred inquiries back to the airline. The FAA did not offer its own explanation in the material we have.

What we cannot say

The research mentions the FAA nationwide ground stop only as context. It gives no date, cause or total for it. So we cannot compare it with the United outage or say how the two relate beyond the passenger's account.

Why the aftermath matters

Even a short incident can leave a trail: rebooked passengers, crews and planes out of position, and queues at customer service. A ground stop's effects can last well beyond the official end. If your business depends on travel, plan for the recovery period, not only the outage itself.

Source: Nine report by Adam Vidler, November 16, 2026 (article link not supplied in the research).


What the Experts Say and What Is Still Unknown

The reporting points one way on cause. Both United and Chase described their problems as operational, not cyberattacks. The retrieved reporting also suggests concentrated dependencies can turn small technical failures into nationwide disruption.

Where the evidence is thin

Be careful with the word "consensus." The "not a cyberattack" statements come from the companies themselves. They are not the result of independent technical analysis. We found no outside forensic review of either incident.

The one independent expert voice in our material is Mike Chapple, a professor of IT, Analytics, and Operations at the University of Notre Dame. As reported by Nine with CNN, he said:

> "The complexity and fragility of the systems that we depend on every day. In each of these cases, what started as an issue in one small part of a larger system quickly spread, causing massive disruptions nationwide."

That is a general comment on fragility. It does not give a root cause for either event.

Where the disagreement is

The disagreement is about scope, not cause. As covered above, AP said United's outage lasted more than 90 minutes, and CNN said about 30 minutes. The flight counts also differ: about 418 delayed at one point versus fewer than 150 affected.

What is missing

  • No dollar amount tied to either incident in the retrieved sources.
  • No regulatory filing tied to this event.
  • No independent root-cause report for United or Chase.

Until those appear, treat the exact size of the damage as unknown.

Source: AP report on the United outage, November 16, AP report on the Chase outage (courant.com), November 16 and Reuters report on Downdetector bank outage reports, November 16

The Chapple quote comes from Nine's report by Adam Vidler, November 16, reported with CNN.


Optimizely Supply-Chain Attack Reached Major Websites

Optimizely helps companies test different versions of a web page, such as two checkout layouts. On November 16, an attacker exploited a flaw in its Experimentation product and added malicious code to some customer projects, the company said. Browsers visiting affected pages could load that code as part of the site. That is a software supply-chain attack: one shared vendor gave the attacker a route to many sites.

Report URI identified 188 affected scripts across 178 organizations. Newsweek’s list includes Zoom, the BBC, CNN, CTV News and Equifax Canada. The code attempted to steal payment card details, redirect cryptocurrency payments and target some iPhones and iPads. The number of visitors who lost data or money remains unknown.

Optimizely said it fixed the flaw and removed the injected code. Reuters reported that Salesforce disabled the scripts as a precaution.

For founders, include A/B testing, analytics and other third-party scripts in your incident plan. Keep a record of which scripts run on checkout and sign-in pages, who owns each integration and how your team can disable it quickly.

Sources: Newsweek’s full list of affected organizations, Reuters reporting, Optimizely’s statement to BleepingComputer.


What This Means for Startups and Small Businesses

You do not need to be an airline or a bank to learn from this. The same chain of events can hit any company that depends on software, payments or partners.

Map your dependencies

List the systems that must work for you to sell, ship and get paid. Include your payment processor, your bank, your support tools and your scheduling software. Note which ones you do not control.

Plan for a "slow" failure, not just a "down" failure

Chase said customers still had access to accounts and funds, but service was slower than usual. Slow failures are easy to miss. Set alerts for delays, not only for full outages.

Have a second path for money

If one bank or payment rail stalls, can you take payment another way? Even a manual backup, such as an invoice link or a second processor, is better than waiting.

Prepare your customer message in advance

Write a short template for outages: what happened, what is affected, what is not, and when you will update. United and Chase both stated early what was not affected. That is a good model.

Separate "not a cyberattack" from "not a problem"

Both companies ruled out a hack early. For customers, that does not remove the harm. Say what you know, and do not claim more than you can prove.

Reduce manual steps

Manual handoffs make outages worse because people must re-enter data and chase updates. Automating routine steps, with clear logs, makes recovery faster and your timeline easier to write down.

Record your own incident timeline

The United gap, 30 minutes versus more than 90, shows how fast facts blur. Log the start, the fix and the follow-up in one place.

Source: AP report on the United outage, November 16 and AP report on the Chase outage (courant.com), November 16

The recommendations are our own editorial advice.


Frequently Asked Questions

Q: What caused the United Airlines outage?

A: United has not given a specific cause in the material we reviewed. It said there was no indication the issue was cybersecurity-related. Nine's report described the problem as affecting its weight check system.

Q: How long did the United Airlines outage last?

A: It depends on the source. AP reported the outage lasted more than 90 minutes, while CNN, as summarized in our research, reported about 30 minutes.

Q: How many United flights were delayed in the outage?

A: FlightAware showed about 418 United flights delayed at one point, according to Nine. CNN, as summarized in our research, reported fewer than 150 flights were affected, so the total is source-dependent.

Q: Were flights in the air affected by the United Airlines outage?

A: No. United said flights already in the air were not affected, and United Express regional flights were also unaffected, according to AP.

Q: Was the United Airlines outage a cyberattack?

A: United said there was no indication the issue was cybersecurity-related. That is the company's statement, and we found no independent investigation confirming the cause.

Q: What was the JPMorgan Chase software bug?

A: Chase said it had a temporary issue related to a software bug in an on-premise hardware system, according to AP. It said the problem was not cyber-related, and the source material gives no further technical detail.

Q: Could Chase customers still access their money during the bug?

A: Chase said customers could still access their accounts and funds. It also said it was taking longer than usual to serve some customers.

Q: Why were there Zelle payment delays at other banks?

A: Other banks saw slowness only when they were dealing with JPMorgan Chase, according to AP. US Bank told customers that Zelle payments involving other institutions could be delayed, though its own systems were not directly impacted.

Q: Was Zelle down during the Chase issue?

A: Zelle said its service was operating normally and that it does not hold consumer funds, according to Nine. Delays were reported on payments involving Chase, not as a Zelle network failure.

Q: Was the United outage connected to the FAA ground stop aftermath?

A: A United passenger told Nine the pilot said the outage was separate from the recent nationwide grounding. The FAA acknowledged the United outage but referred questions to the airline, so we have no official confirmation either way.

Additional Links

Flowgrammer.ca – 💡 Unlock AI-Powered Automation! Let flowgrammer.ca handle complex workflows so you can focus on growing your business.

Flowgrammers.ca – 💡 Join Toronto's Fastest Growing AI and Business Automation Community.

OpenClaw Toronto