News for hackers. Stuff that matters.
Re:Chase Bank is now also having a meltdown by danso on Monday November 16, 2026 @03:01PM (#50522335)
Why do people assume that this crash is the result of AI vibe coding (i.e. these companies rolling out buggy production code) versus AI-empowered vulnerability seekers? Seems more likely that a group is trying to swarm and exploit a possible vulnerability common to these banks' operations, than it is that Bank of America, Chase, and U.S. Bank all happened to roll out bad vibe code on Monday.
Re:Chase Bank is now also having a meltdown by sunbum on Monday November 16, 2026 @03:04PM (#50522394)
Hanlons razor. “Never attribute to malice that which is adequately explained by stupidity.”
Re:Chase Bank is now also having a meltdown by password54321 on Monday November 16, 2026 @03:11PM (#50522483)
Heuristics are not proof and this is probably one of the more flawed/lazy ones.
Re:Chase Bank is now also having a meltdown by sanderjd on Monday November 16, 2026 @03:43PM (#50522975)
I think we need a new razor: "Never attribute to AI incompetence that which is adequately explained by human incompetence."
Re:Chase Bank is now also having a meltdown by djeastm on Monday November 16, 2026 @04:10PM (#50523318)
"There's three ways to do things. The right way, the wrong way, and the Max Power way!"

"Isn't that the wrong way?"

"Yeah, but faster!"

Re:Chase Bank is now also having a meltdown by dclowd9901 on Monday November 16, 2026 @04:55PM (#50523912)
If companies are forcing their employees to use AI, which human's incompetence is at play?
Re:Chase Bank is now also having a meltdown by sanderjd on Monday November 16, 2026 @05:48PM (#50524605)
Probably multiple humans, I would say!
Re:Chase Bank is now also having a meltdown by SAI_Peregrinus on Tuesday November 17, 2026 @11:50AM (#50534257)
SAI's razor: Never attribute to stupidity that which is adequately explained by greed.
Re:Chase Bank is now also having a meltdown by fedpost on Monday November 16, 2026 @03:09PM (#50522462)
I don't think the average person cares tbh.

It's caused my AI, it doesn't really matter who's fault it is

Re:Chase Bank is now also having a meltdown by Ancalagon on Monday November 16, 2026 @03:10PM (#50522468)
Little hispanic girl voice: "Por que no los dos?"
Re:Chase Bank is now also having a meltdown by superfrank on Monday November 16, 2026 @03:12PM (#50522489)
Because there’s a lot of anti-ai sentiment going around right now. Blaming it on AI slop code supports pre-existing beliefs that AI is useless. If it’s AI hackers then that not only means AI is actually good at something, it’s potentially an argument for why we need increased spending and that there really is a race dynamic at play that we need to win.

Basically, blaming AI slop supports a lot of pre-existing beliefs, while blaming AI hackers does not.

Re:Chase Bank is now also having a meltdown by jenniferhooley on Monday November 16, 2026 @03:41PM (#50522957)
I don't really think it's that. From the people I work with, it's more the push beyond the "capabilities" of AI to the point that we have this amazing tool (AI), which theoretically should allow us to ship much better and more resilient systems. But instead we are pushed to ship really cruddy systems without the proper amount of diligence, review, and testing due to the C-suite's desperation to ship as fast as possible - consequences be damned.
Re:Chase Bank is now also having a meltdown by preg_match on Monday November 16, 2026 @09:17PM (#50526567)
Yeah this is how I view it too.

AI really does have the potential to make software more robust and higher quality than ever before. We can write more tests, new kinds of tests, do pen testing, do deeper analysis of code. But we're not. This, like software before, is a slop machine. It's about getting things to kind of work just enough that customers are, very temporarily, dazed, and sales are able to sell it. It's a house of cards situation and all we've done is starting stacking more cards on faster.

Re:Chase Bank is now also having a meltdown by Aperocky on Monday November 16, 2026 @03:13PM (#50522503)
The initial postmortums are out already for the 2 previous event, and they appear to have nothing to do with vulnerability.
Re:Chase Bank is now also having a meltdown by werdnapk on Monday November 16, 2026 @03:15PM (#50522537)
Do you really believe a guy doing some wiring caused an air traffic shutdown last week?
Re:Chase Bank is now also having a meltdown by shermantanktop on Monday November 16, 2026 @03:29PM (#50522774)
[delayed]
Re:Chase Bank is now also having a meltdown by takeda on Monday November 16, 2026 @03:29PM (#50522775)
Not wiring, the new AI slop system was making a lot of queries effectively DDoSing the existing system.
Re:Chase Bank is now also having a meltdown by ragequittah on Monday November 16, 2026 @04:01PM (#50523209)
This right here is what needs to stop. AI has its problems but everyone blaming everything on AI is starting to wear thin. By all reports the new SMART AI system wasn't even in any way connected to the network that went down[1]. I guess we can put our tinfoil hat on and say every problem we have from now on is AI's fault and nobody will report it, but I'm not sure that helps anything. Probably better to wait and try to see what actually happened [2] before our knees jerk and credibility gets lost for when actual AI problems occur.

[1] https://apnews.com/article/faa-smart-ai-outage-08af345749c81...

[2] https://www.faa.gov/newsroom/nationwide-ground-stop-question...

Re:Chase Bank is now also having a meltdown by Forgeties79 on Monday November 16, 2026 @04:13PM (#50523360)
Can you blame people for not trusting government officials when for the last decade Trump and co have been doing everything in their power to make sure people don’t trust government officials?
Re:Chase Bank is now also having a meltdown by ragequittah on Monday November 16, 2026 @04:26PM (#50523517)
Not at all. But the AI would've had to be doing something completely different than its function. It doesn't send or receive data to the system that was overloaded, it's built to receive data from a completely different system. I also think this would be analyzed by enough people that one of network engineers or someone who just generally hates the idea of AI in their workload would've come out and said something by now.

Don't counter lack of credibility by spreading information you can't verify. It just muddies the water even more. There's people out there right now who think it's the AI apocalypse because a banking system is a bit slower.

Re:Chase Bank is now also having a meltdown by Forgeties79 on Monday November 16, 2026 @04:41PM (#50523697)
I didn’t spread anything. I just think people are inclined to think it’s whatever this current administration says it isn’t. I don’t blame them. There is no shared reality anymore, everyone is basically a little conspiracy theorist
Re:Chase Bank is now also having a meltdown by randomNumber7 on Monday November 16, 2026 @05:46PM (#50524572)
It will get better at some point. When Trump is away I promise you to blindly trust the government again.
Re:Chase Bank is now also having a meltdown by takeda on Tuesday November 17, 2026 @03:00PM (#50537266)
It needs data to function and since it is LLM more likely they they implemented MCP that starting DDoSing the rest of the system when LLM was being asked for every single flight.

> It doesn't send or receive data to the system that was overloaded, it's built to receive data from a completely different system.

You're adding your own assumptions. This is what they said:

> Q: Was this caused by SMART system?

> A: No. The two systems are not related. SMART is a data aggregator, and it does not feed information into the air traffic control system.

It doesn't feed data, they didn't say it is completely isolated, which fits what I wrote.

They absolutely have incentive to avoid investigation that the company that donated to Duffy's son in law received nearly a billion no bid contract and failed to deliver a working product.

Re:Chase Bank is now also having a meltdown by Forgeties79 on Tuesday November 17, 2026 @03:11PM (#50537478)
I looked into your claim about the son-in-law, and it seems you’re kind of right but mostly wrong. It looks like there were about a dozen bids for the contract and he does not own the company. But he is definitely involved in the company that received the contract.

Now don’t get me wrong, Duffy could totally be running cover for him and that is certainly the kind of corruption I expect from this administration. But the details are not quite as severe and direct as you are making them out to be it seems.

Re:Chase Bank is now also having a meltdown by fwip on Monday November 16, 2026 @04:30PM (#50523579)
Hang on - that first link says: "there’s no indication the communications issues that caused the ground stop are linked to the new computer system,"

As near as I can tell, they are saying that the communication issues are not related to the new computer system (not causative) - not that the new system is physically disconnected from the communications network.

(The article is a bit confusing, using "connected" and "linked to", which could either be describing physical or causative relationships).

Re:Chase Bank is now also having a meltdown by ragequittah on Monday November 16, 2026 @04:54PM (#50523890)
FAA's site says:

Q: Was this caused by SMART system? A: No. The two systems are not related. SMART is a data aggregator, and it does not feed information into the air traffic control system.

If you dig a bit further the aggregator gets its data from SWIM, which receives (but does not send) data from the system that went down. I believe it's a 1 way VPN connection that they use to aggregate data because SWIM is consumer facing as well.[1]

So unless something went terribly wrong the AI couldn't have had anything to do with it. But that won't stop it being the top narrative for all time because nobody will look into it this far and we no longer believe any official stories about anything.

[1] https://www.faa.gov/air_traffic/technology/swim/sfdps

Re:Chase Bank is now also having a meltdown by fwip on Monday November 16, 2026 @05:01PM (#50524000)
Thanks - I appreciate the clarification. :)
Re:Chase Bank is now also having a meltdown by takeda on Tuesday November 17, 2026 @02:45PM (#50537103)
Except on Friday Mullin accidentally said that (when there was a question about attack) it happened after the system was patched and you can on Duffy's face that he was not supposed to say that.

Then next day they had conference where they came up with the maintenance guy.

Are you truly believe that a guy replacing a switch somewhere in Arkansas can just shut down the whole air travel in the entire country? The biggest disruption since 9/11 25 years ago? And just happened a day after SMART was deployed.

We are on tech forum, I would assume I'm talking to tech people who I hope understand how networking equipment operates.

Re:Chase Bank is now also having a meltdown by motionlessveloc on Monday November 16, 2026 @03:33PM (#50522830)
Yes, at least in a "straw that broke the camel's back" sense.

Chernobyl was caused by a guy flipping a switch, Challenger blew up because of a faulty O-ring, etc.

Re:Chase Bank is now also having a meltdown by DaiPlusPlus on Monday November 16, 2026 @03:38PM (#50522921)
That is all true, but those shouldn't be the stated reason that's reported to the masses in a press-conference headed up by a US departmental head.

I also wonder if Trump's administrations' spokespeople even realize they have a massive credibility problem, and that if they want people like me to believe anything then I have to hear it from a mid-level functionary, not a political appointee.

Re:Chase Bank is now also having a meltdown by pantulis on Monday November 16, 2026 @03:50PM (#50523059)
Proper root cause analysis takes its time so the last obvious fail in the chain of events is what gets published quickly.
Re:Chase Bank is now also having a meltdown by Forgeties79 on Monday November 16, 2026 @04:06PM (#50523281)
I don’t think it’s fair to blame people trying to publish quickly after that absolute disaster of a press conference we saw the other day which only led to even more confusion. They said it was and wasn’t several things, constantly contradicting themselves and shedding no light on the situation (when they weren’t busy sniffing Trump’s farts).
Re:Chase Bank is now also having a meltdown by augment_me on Monday November 16, 2026 @03:50PM (#50523068)
You are in a minority, and no-one cares anymore.

You say whatever makes your stocks go up and now down, and if you don't, you are stupid because it's normalized now, there are no repercussions, and if you don't someone else will.

Re:Chase Bank is now also having a meltdown by ignore on Monday November 16, 2026 @04:05PM (#50523265)
If the mid-level functionary tacks on, "This is why we demand that Congress allocate $50 billion in new funding for modernization!" do you still believe them?
Re:Chase Bank is now also having a meltdown by DaiPlusPlus on Monday November 16, 2026 @07:45PM (#50525859)
> If the mid-level functionary tacks on, "This is why we demand that Congress allocate $50 billion in new funding for modernization!" do you still believe them?

Of course not, but that's the point of wanting to hear something from someone lower in the org chart: people lower-down on the totem-pole have fewer things within their remit that they can credibly talk about publicly; so if they ever speak of things above-their-pay-grade (like a technical team manager giving an official statement concerning departmental-level funding) then it's a signal they aren't speaking honestly.

Re:Chase Bank is now also having a meltdown by hunterpayne on Monday November 16, 2026 @04:13PM (#50523364)
"Chernobyl was caused by a guy flipping a switch"

No, just no...Chernobyl was caused by the staff doing an experiment that to put it mildly was wildly risky. They disabled safety systems with wrenches (meaning they couldn't easily be reenabled). Challenger blew up because staff at NASA ignored warnings from the people who made the O-rings. Saying these were "straws" is completely irresponsible. Attitudes like this are what cause outrages. Also, unless you are being dishonest, this is the worst string of outrages in the history of tech. There is a cause. It can be found. And unless you think in these terms, you have no business working with a production system in any way.

Re:Chase Bank is now also having a meltdown by Liuser on Monday November 16, 2026 @04:33PM (#50523617)
You’re not in disagreement with op. That’s the point motionlessveloc is making, it’s a series of mistakes that points to a broader systemic problem.
Re:Chase Bank is now also having a meltdown by fwip on Monday November 16, 2026 @04:34PM (#50523619)
[delayed]
Re:Chase Bank is now also having a meltdown by brendoelfrendo on Monday November 16, 2026 @03:37PM (#50522900)
I can really believe that they plugged in a misconfigured router and that a new router on a faster link was able to flood downstream legacy hardware with junk requests to the point where it started to fail.
Re:Chase Bank is now also having a meltdown by tiahura on Monday November 16, 2026 @04:25PM (#50523512)
Are RIP and BGP still a thing?
Re:Chase Bank is now also having a meltdown by cestith on Monday November 16, 2026 @04:42PM (#50523713)
BGP4 is only still a thing on The Internet.
Re:Chase Bank is now also having a meltdown by brendoelfrendo on Monday November 16, 2026 @07:22PM (#50525657)
BGP is very much a thing, and increasingly used inside larger networks instead of just on the edge. RIP should very much be dead, but probably isn't. Afaik OSPF is the interior routing protocol of choice for situations where iBGP isn't used.
Re:Chase Bank is now also having a meltdown by mh- on Monday November 16, 2026 @03:38PM (#50522916)
Do I believe a change in networking caused a networking issue? Yes?
Re:Chase Bank is now also having a meltdown by DaSHacka on Monday November 16, 2026 @03:40PM (#50522945)
Do you have any reason to believe it didn't?
Re:Chase Bank is now also having a meltdown by icepush on Monday November 16, 2026 @03:46PM (#50523008)
I don't know, do computers use wires ???
Re:Chase Bank is now also having a meltdown by tygon on Monday November 16, 2026 @03:48PM (#50523039)
While AI rollouts have had issues, it is far from safe to assume just because there is an issue, it is automatically AI-related or vibe code specifically. Things always are breaking. Lines go down, servers have power failures, etc.
Re:Chase Bank is now also having a meltdown by cgio on Monday November 16, 2026 @03:57PM (#50523138)
I think it is the co-occurrence of many incidents across different industries that points to potentially common causality.
Re:Chase Bank is now also having a meltdown by dclowd9901 on Monday November 16, 2026 @04:53PM (#50523873)
With this level of frequency and breadth? The _only_ common factor is AI implementation.
Re:Chase Bank is now also having a meltdown by tygon on Monday November 16, 2026 @05:32PM (#50524404)
The trend is your friend until it bites your rear end. To give a topical answer, the Outlook issues were blamed on a software bug from months ago. While AI is being embraced en masse and causing all manner of issues, we have AI issues as _well_ as traditional "it broke" moments. Isn't it fun?
Re:Chase Bank is now also having a meltdown by schiffern on Monday November 16, 2026 @03:53PM (#50523095)

  >Do you really believe
Thanks, conspiratorial thinking hadn't annihilated my last brain cell yet
Re:Chase Bank is now also having a meltdown by tiahura on Monday November 16, 2026 @04:28PM (#50523550)
LAX outage is blamed on a single computer

https://www.latimes.com/travel/la-trw-laxdelays15aug15-story...

By Tami Abdollah Aug. 15, 2007 12 AM PT

U.S. Customs officials said Tuesday that they had traced the source of last weekend’s system outage that left 17,000 international passengers stranded in airplanes to a malfunctioning network interface card on a single desktop computer in the Tom Bradley International Terminal at LAX.

The card, which allows computers to connect to a local area network, experienced a partial failure that started about 12:50 p.m. Saturday, slowing down the system, said Jennifer Connors, a chief in the office of field operations for the Customs and Border Protection agency.

As data overloaded the system, a domino effect occurred with other computer network cards, eventually causing a total system failure a little after 2 p.m., Connors said.

Re:Chase Bank is now also having a meltdown by solyin on Monday November 16, 2026 @04:37PM (#50523661)
Running Window 98 SE.
Re:Chase Bank is now also having a meltdown by BeratnasGas on Monday November 16, 2026 @04:45PM (#50523756)
I automatically trusted the accuracy/honesty of this explanation from 2007. Zero trust today. We have much to fear from fear itself.
Re:Chase Bank is now also having a meltdown by forshaper on Monday November 16, 2026 @04:28PM (#50523551)
It's the sort of thing that is common in all systems I've been inside- which is to say, something little, to do with configuration, hardware fiddling, etc.
Re:Chase Bank is now also having a meltdown by werdnapk on Tuesday November 17, 2026 @08:24PM (#50540687)
Hilarious how I got down voted for this comment as multiple other networks and systems start going down all over the place. So many wiring jobs going on I guess.
Re:Chase Bank is now also having a meltdown by greenchair on Monday November 16, 2026 @04:17PM (#50523417)
my sweet summer child
Re:Chase Bank is now also having a meltdown by DEF14A on Monday November 16, 2026 @04:50PM (#50523826)
What a snarky, condescending thing to say.
Re:Chase Bank is now also having a meltdown by eliago on Monday November 16, 2026 @05:24PM (#50524291)
I personally thought it was humorous but I can see the perception.
Re:Chase Bank is now also having a meltdown by Aperocky on Monday November 16, 2026 @08:00PM (#50525989)
The reliability of reports today are generally poor, however, a technical person can tell relatively easily as to whether the report is likely to happen vs. unlikely. And if it involves the simplest thing that could go wrong gone wrong, then that's usually the right explanation. Otherwise known as Occam's Razor.

A deployment on Friday screwed things up vs. an adversarial attack which involved multiple agency needing to cover up together with unclear motive and huge risk down the line? It's an easy pick.

Re:Chase Bank is now also having a meltdown by eliago on Tuesday November 17, 2026 @12:23PM (#50534841)
I would not underestimate the US government coverup abilities, especially when the department of homeland security is involved. I do agree it is most likely incompetence though.
Re:Chase Bank is now also having a meltdown by itishappy on Monday November 16, 2026 @03:18PM (#50522590)
I'd assume that whatever happened affected a single centralized service that these banks all relied upon.
Re:Chase Bank is now also having a meltdown by tedd4u on Monday November 16, 2026 @03:22PM (#50522642)
Like everything else it’s probably a combination of both (as well as other causes).
Re:Chase Bank is now also having a meltdown by bottlepalm on Monday November 16, 2026 @03:24PM (#50522686)
Everyone is vibe coding now. It's not just you. It's not an assumption.

Vibe coding, vibe reviewing, vibe fixing. No one has a clue how software works anymore.

Re:Chase Bank is now also having a meltdown by snorkel on Monday November 16, 2026 @03:55PM (#50523118)
… and no one wants to work anymore! Back in my day we’d hand assemble code on paper and then whistle it over the phone to a 300 baud teletype in the server room … and that shit never broke! Not once!
Re:Chase Bank is now also having a meltdown by bottlepalm on Monday November 16, 2026 @09:47PM (#50526759)
The difference is back then there was usually someone that understood the system and could fix it.

Now, no one does. We ask AI to figure it out and fix it. What happens if the AI goes down?

Re:Chase Bank is now also having a meltdown by Ancalagon on Monday November 16, 2026 @03:42PM (#50522960)
Why can't it be both?
Re:Chase Bank is now also having a meltdown by bdcravens on Monday November 16, 2026 @03:50PM (#50523057)
Because people want to believe that AI code is inferior, and that it's about to go poof with a return to the previous status quo.
Re:Chase Bank is now also having a meltdown by Grimblewald on Monday November 16, 2026 @03:57PM (#50523150)
it is though. at minimum qa/QC of ai code is way worse. Things are hitting prod right now in many sectors that should never have hit prod. Amazon on mobile (at least android + ff) is unusable ATM as the most recent example.
Re:Chase Bank is now also having a meltdown by 1970-01-01 on Monday November 16, 2026 @03:59PM (#50523177)
Just like humans, it varies wildly. Stating anything other than that is speculation at best.
Re:Chase Bank is now also having a meltdown by bdcravens on Monday November 16, 2026 @04:04PM (#50523253)
This gets to the implied argument: that humans are inherently better to machine-generated output. The truth is there are a ton of programmers getting paid well to generate crap. Anyone's who been a part of any team that isn't some highly curated A-squad knows this is true. Hell, even teams of 1 know it to be true, when you were rushed, didn't understand the domain or stack, under personal pressure etc.
Re:Chase Bank is now also having a meltdown by Grimblewald on Monday November 16, 2026 @07:38PM (#50525793)
I never implied human was better, im sure AI can and does generate better code. The problem is mostly better doesn't mean always better, and the issue here is Qa/Qc is gone, because of this "ai code is better" assumption. With it came a deluge of bugs that no longer get caught. We all see it everywhere, all the time, im bot syre why this take of mine is in anyway controversial?
Re:Chase Bank is now also having a meltdown by Creamsicle47 on Monday November 16, 2026 @04:05PM (#50523264)
Except human code is reviewable at a reasonable speed
Re:Chase Bank is now also having a meltdown by Grimblewald on Monday November 16, 2026 @07:36PM (#50525775)
All I know is I used to assume my device is malfunctioning when things didnt work, but given how common place broken UI's have become, my devices are now rarely the suspected point of failure.
Re:Chase Bank is now also having a meltdown by swozey on Monday November 16, 2026 @04:29PM (#50523559)
Before laying off half of my company the last place I worked fired QA first
Re:Chase Bank is now also having a meltdown by JsonDemWitOster on Monday November 16, 2026 @04:00PM (#50523205)
I know the leg I'm standing on is correlation but did we have such widespread outages pre-LLMs? The two that come to mind is that one time some intern pushed a config change that borked us-east-1 and Gitlab deleting their DB. And both had clear comms on the situation within acceptable time frames.

Also, I don't think it's that "AI code is inferior" but rather devs got sloppy and no longer review code. Not to say that everyone's lazy but me---a lot of systemic/environmental factors could be the reason.

Re:Chase Bank is now also having a meltdown by fourside on Monday November 16, 2026 @04:07PM (#50523287)
But that’s the point around correlation =/= causation. What the parent comment is saying is that the cause could be that attackers have much more sophisticated tools to bring down services. The timing with AI adaption doesn’t prove on its own that lower code quality is the reason.
Re:Chase Bank is now also having a meltdown by dghlsakjg on Monday November 16, 2026 @04:07PM (#50523290)
Large outages are not a new thing.

People were making memes about the GitHub unicorn a decade ago.

Re:Chase Bank is now also having a meltdown by JohnMakin on Monday November 16, 2026 @04:11PM (#50523340)
No one is saying they are, they’re asking whether the frequency and scale has changed.
Re:Chase Bank is now also having a meltdown by bdcravens on Monday November 16, 2026 @04:18PM (#50523436)
It absolutely has. The "why" is a matter of first-party versus third-party (bad AI code making bad services, or good services unable to handle the load from everyone else pushing AI code, or a combination of the two)
Re:Chase Bank is now also having a meltdown by esseph on Monday November 16, 2026 @04:23PM (#50523488)
[delayed]
Re:Chase Bank is now also having a meltdown by jeremyjh on Monday November 16, 2026 @04:54PM (#50523897)
Or, the thing that has happened on a huge scale in much less time than decades.
Re:Chase Bank is now also having a meltdown by esseph on Monday November 16, 2026 @06:05PM (#50524836)
[delayed]
Re:Chase Bank is now also having a meltdown by tadfisher on Monday November 16, 2026 @04:21PM (#50523466)
With GitHub specifically, yes. But I remember AWS/GCP/Azure outages were like a yearly occurrence before the 2020s, and we kept having the same conversations back then about infrastructure resilience, multi-cloud, etc. that were too hard to address then and still too expensive to address now.
Re:Chase Bank is now also having a meltdown by jeremyjh on Monday November 16, 2026 @04:54PM (#50523887)
Maybe one major platform had a major outage annually but AWS certainly didn't have a major outage every year. More like every 3-4 years. I remember exactly two in the last 10 years that impacted the production application I run.
Re:Chase Bank is now also having a meltdown by tyre on Monday November 16, 2026 @05:16PM (#50524181)
There have been many more than two in the past ten years. Maybe not for you, but depending on the region/AZ, especially us-east-1 as it’s aged, outages are impossible to avoid.

Much better than Azure, but that’s not a high bar.

Re:Chase Bank is now also having a meltdown by jeremyjh on Monday November 16, 2026 @07:10PM (#50525503)
How many made the front page of hacker news and featured on major broadcast networks? Because that is the level of incident we're talking about here.
Re:Chase Bank is now also having a meltdown by dghlsakjg on Monday November 16, 2026 @07:06PM (#50525459)
Here’s a timeline of major AWS outages: https://awsmaniac.com/aws-outages/

Just because an outage doesn’t affect your specific app doesn’t mean it didn’t happen. By that logic Microsoft didn’t have an outage last week since my windows gaming pc was fine.

Re:Chase Bank is now also having a meltdown by jeremyjh on Monday November 16, 2026 @07:08PM (#50525487)
We're not really talking about the same things here. I'm talking about the outages where dozens or hundreds of known platforms are down and it makes the front page of HN and major media coverage. That is the magnitude of many of these recent incidents.

I know there are more incidents than that.

Re:Chase Bank is now also having a meltdown by joesb on Monday November 16, 2026 @05:46PM (#50524574)
But how do we know it is because of AI vibe coding though?

It could be because some critical infrastructure are due to upgrade after a long delay and this is inevitable at some point.

It could be that AI agentic hacking has pushed for some rearchitecture in faster deployment time, which may result in big outage for industry that has so much legacy and used to big bulk deployment only.

Or it could just be because we rely more on cloud infrastructure than previously.

Re:Chase Bank is now also having a meltdown by bdcravens on Monday November 16, 2026 @04:10PM (#50523331)
Failures aren't just a product of AI-written code in the infrastructure, but the infrastructure trying to bear the load of everyone else's AI-written code at massive scale.
Re:Chase Bank is now also having a meltdown by theseamusjames on Monday November 16, 2026 @04:56PM (#50523923)
The crowdstrike outage was much much bigger, both in reach and in impact. It took days to weeks to recover from.
Re:Chase Bank is now also having a meltdown by CptKriechstrom on Monday November 16, 2026 @05:06PM (#50524069)
Remember when AWS messed up their BGP Routes?
Re:Chase Bank is now also having a meltdown by freecodeio on Monday November 16, 2026 @04:04PM (#50523252)
blaming this problem to vibe coding != ai bad at code

shit programmers have always been a thing, these same shit programmers now putting output from claude straight to production

on top of this there are literally PMs getting involved and doing their own PRs, see vscode recently

Re:Chase Bank is now also having a meltdown by paimapi on Monday November 16, 2026 @04:12PM (#50523351)
It's not that AI code is inherently inferior, it's that the bulk of the work engineering does now is code review and the scale of reviews has become exponential which means a lot of stuff just gets punted to agents and not carefully examined by anybody with actual subject matter expertise. Plus automation and platform work (like managing test suites) has also similarly become deprioritized and QA in general is being obsoleted as a field (for worse, really).

This is a systemic issue that's driven by AI but the responsibility lies with leadership who are still operating on the move fast and break things mentality.

Re:Chase Bank is now also having a meltdown by jeremyjh on Monday November 16, 2026 @04:57PM (#50523932)
Also most engineers have always been terrible at reviewing code. They could find most bugs when working through it line by line manually as they wrote the code and the tests, but most could never find bugs in their peer's code through inspection. Now that this - along with business and product understanding - are the primary skills they need, a lot of developers are under-skilled for their job requirements as they suddenly exist today.

Staff-level engineers can do this work because they always have, but if they are suddenly the only ones who can in an org then they are simply overwhelmed.

Re:Chase Bank is now also having a meltdown by uludag on Monday November 16, 2026 @04:21PM (#50523469)
Or maybe that cyber attacks are generally known after the fact that they are cyber attacks via things like extortion.

Like take the Binance hack for example. A naughty hacker, instead of stealing bitcoin, could have just caused mass outage and disruption without stealing anything, but didn't because bad actors usually want some financial benefit.

Like if we learn that PII was stolen, then it's be safe to say that this was a cyber attack.

Re:Chase Bank is now also having a meltdown by EricDeb on Monday November 16, 2026 @04:23PM (#50523493)
No the issue with AI code is not that it's inferior but that it solves the wrong problem or doesnt believe an edge case is necessary or other contextual issues unrelated to whether the code is actually correct as written.
Re:Chase Bank is now also having a meltdown by Barrin92 on Monday November 16, 2026 @04:24PM (#50523501)
>Because people want to believe that AI code is inferior,

This is armchair psychology and extremely bad one because the people who have been concerned with engineering quality have been vastly outnumbered by people who just want to be able to turn their brain off and "ship fast" for probably 15+ years, and that's been reflected in reliability long before LLMs came around.

The code these systems churn out at scale is absolute trash but the financial incentives are to produce out more of it because nobody is ever actually held liable for software breaking in our age

Re:Chase Bank is now also having a meltdown by fock on Monday November 16, 2026 @05:00PM (#50523982)
yes, I read some java today where I wished for the clankerd to have done it...

Think system(curl) and random-if-cascades which are never reached - they removed the system(python) in this iteration though...

At this point I think AI-code is just average and probably just fine for corporate environments/SaaS (especially given what thkse produce today), but I still think infrastructure should be a) understood by humans b) produced without installing a backdoor on the dev machine and c) a human should decide what to build and be able to reign in the machine.

Re:Chase Bank is now also having a meltdown by lbrito on Monday November 16, 2026 @04:42PM (#50523720)
That's just a strawman argument.

While there may be people arguing for that, the more relevant point is that regardless of any possible positives of AI code, there are clear negatives that are being largely ignored. Specifically in such outage cases, the volume of code being put into production with little or no review or understanding.

Re:Chase Bank is now also having a meltdown by rs999gti on Monday November 16, 2026 @05:08PM (#50524087)
AI code is inferior, but business, the media, and regular people don't care about that. They just want fast and cheap, so you get the slop code you pay for.
Re:Chase Bank is now also having a meltdown by Loughla on Monday November 16, 2026 @05:12PM (#50524143)
I find it fascinating that anyone thinks computer programs will be different than anything else.

Clothes. Food. Appliances. Tools. Electronics.

All of these things got worse, but got WAY cheaper. All of these industries had to shed excess labor like crazy in pursuit of optimization at the cost of quality.

Why would coding be different?

Re:Chase Bank is now also having a meltdown by randomNumber7 on Monday November 16, 2026 @05:32PM (#50524405)
Because you write a program once and then you can sell copies without extra costs per unit you sell.
Re:Chase Bank is now also having a meltdown by shoobiedoo on Monday November 16, 2026 @05:17PM (#50524207)
I don't know if it's as much as people just hoping that it fails, or the fact that in my opinion a programmer is far more likely to verify code that their reputation might depend on instead of just shoveling in whatever an agent spits out.
Re:Chase Bank is now also having a meltdown by whateveracct on Monday November 16, 2026 @05:55PM (#50524707)
if only...
Re:Chase Bank is now also having a meltdown by pessimizer on Monday November 16, 2026 @06:14PM (#50524939)
> Because people want to believe that AI code is inferior

No, people want to believe that it is good, despite all evidence. However the status quo will not be returning, because it will get better. The catch is that it will somehow end up in your pacemaker or the brakes on your car while it still sucks.

Re:Chase Bank is now also having a meltdown by surgical_fire on Monday November 16, 2026 @03:57PM (#50523145)
"AI cannot fail, you can only fail at AI".

Somehow I knew I would find something like this on this comment section.

Re:Chase Bank is now also having a meltdown by codingdave on Monday November 16, 2026 @04:21PM (#50523477)
From the article: "...a technical issue at JPMorgan Chase caused ripple effects throughout the financial system."

Nobody is claiming multiple parallel failures. They are claiming one failure that impacted multiple organizations.

Re:Chase Bank is now also having a meltdown by dclowd9901 on Monday November 16, 2026 @04:51PM (#50523837)
The companies in question have confirmed it wasn't due to cyber attacks. That's why.

What's it going to take for the AI pushers to see that maybe this isn't the road to go down.

Re:Chase Bank is now also having a meltdown by rs999gti on Monday November 16, 2026 @05:06PM (#50524055)
> AI vibe coding

What's new? What has been operating fine until the AI, cloud, and centralized computing came onto the scene?

Re:Chase Bank is now also having a meltdown by rewgs on Monday November 16, 2026 @05:31PM (#50524383)
IMO the problem is not AI-generated code per se, but rather the utterly absurd expectations and resulting destruction of best-practices and discipline that developers all over are now dealing with.

My first thought for this week's outages has been that people are moving too fast and are, as the saying goes, breaking things.