Note than any of the core processes there likely run on very old but very reliable mainframes and associated software stacks (think COBOL, CICS, IMS, DB/2 on 390).
More (non-technical):
<a href="https://www.rocketsoftware.com/en-us/insights/why-financial-institutions-are-modernizing-mainframe-and-how-start-process" rel="nofollow">https://www.rocketsoftware.com/en-us/insights/why-financial-...</a>
- Cards not working.<p>- Physical branches closed or unresponsive.<p>- Online banking down.<p>This exact same thing happened in Europe with Revolut late last month. It was resolved in about 12 hours: <a href="https://www.revolut.com/blog/post/20octoutagetechnicaloverview/" rel="nofollow">https://www.revolut.com/blog/post/20octoutagetechnicalovervi...</a><p>In that case, it was a Google Cloud outage. Something similar (database outage) could be the culprit here.
Lots of banks have been down at various times, but its a lot more of a problem when multiple major banks are down at the same time.
Here in Canada, about 4 years ago, we had an outage where cards weren't working for many hours at any store due to a huge Rogers outage.
article says it's mainly Zelle
Its wild that even our banks are now reliant on cloud providers.
It doesn’t seem like a cloud provider was at fault:<p>> “JPMorgan Chase has experienced a temporary issue related to a software bug in an on-premise hardware system — it is not cyber-related,” said Joe Evangelisti, spokesman for the bank.
It's wild that they pay like shit and attract 2nd rate programmers.<p>Eh, actually, I don't know if that's true about 2nd rate programmers, in a lot of ways they're probably better, but they do get paid less.<p>I realized this while working at a startup. The startup had a webpage that worked half the time--that's it, that's why we had funding. Well, that and the founder was going around telling investors we had fancy AI algorithms, which were actually mostly manual human work.<p>Meanwhile my friend working at the bank made a lot less.
[flagged]
I’ve always found it curious that FAANG/California-based employees receive comments of “hugs” from HN during periods of downtime, while those outside of the bubble receive only mild slander. Of course, no suggestion that you specifically have engaged in the former.
I've got my cash stash.
I’ve got hella weed
That will work for the first week to month of a disaster. Once people realize it's bigger then dollars will rapidly lose value compared to direct barter for useful things.
I don’t think cash is gonna help if the entire monetary system stops working - gold maybe?
If the “entire monetary system” stops working, then things are fucked enough already that gold is essentially the same in terms of utility as cash would be, in that its only immediate value is its scarcity.<p>Things like food, water, basic sanitary items, would be bartered for.
There are countries where the monetary system basically is cash (lots of people don’t have bank accounts).<p>There are definitely issues with that, but it does work in the sense that people can buy and sell things and survive, provided the government is competent enough to provide good quality notes and coins and resists the temptation to print too many.<p>After all it’s how western societies worked throughout human history until relatively recently
It is pretty common to for credit card systems to go offline temporarily at grocery stores and restaurants. Always a good idea to have cash.
I haven't carried enough cash to pay for groceries or dinner at a restaurant in over 10 years.
Because credit-card systems ostensibly don't rely on debiting actual funds, they should be resilient and continue to work offline; when you use EMV (chip+PIN) it's the card that authenticates you and authorizes the transaction, not the bank down a phone-line (and who can forget credit-card imprinter machines?)
Bullets and shotgun shells.
lead maybe
<i>I don’t think cash is gonna help if the entire monetary system stops working - gold maybe?</i><p>Yeah, I'll just get out my pocket knife and carve a little chunk off that big bar of gold when I'm trying to barter for gas at the truck stop. That'll work.
I would happily trade people for gold because there is no way at all they would ever get even close to the value of their gold in goods. You could probably get thousands of dollars worth for some beans by time they decide to start trading away their gold.<p>Doesn't help if the world truly goes to shit and doesn't recover for decades, but if there is any kind of recovery then the gold would be worth something again.
Gold is good. You need a fairly large chunk to bludgeon the marauding hordes though.
I only carry gold pressed latinum
I prefer ammo, canned goods, solar panels, and a well. And maybe a doctor or nurse practitioner friend.
can't eat gold
You can't send a single cent of your physical cash over the internet into someone else's bank account who is also experiencing this outage. FedNow is likely not working either.<p>On the other hand stablecoins such as USDC can be sent over the internet on blockchains such as Tempo, Solana, XRP and Stellar worldwide, 24/7 in less than 5 mins and with extremely low fees.<p>To Downvoters: Come on. You cannot send your physical paper dollar notes to someone else in another state or around the world in less than 5 seconds.<p>I'd be annoyed if I was a BOA or Chase customer too. But the truth is that blockchains such as Tempo continue to work anyway worldwide 24/7 without fail.
Strangely enough for me (with Chase):<p>- Cards working<p>- Branches (the few we have left) open, or at least it was when I drove by at lunch<p>- Online banking has been working for me all day.
My nontechnical co-workers see the Microsoft 365 outage, the FAA ground stop, and things like this as one interconnected problem. They aren't entirely wrong, but the general fear is hard to dismiss
They are at least interconnected in the sense that we are struggling societally to do big, hard things that we could do a decade ago.<p>Roman citizen wondering why the aqueduct isn’t working kind of thing.
Interestingly enough it took about four generations, a century, for someone to go back in and investigate the aqueducts properly. I think a lot of this is due to previously easy, simple things being ignored, in part because they are considered menial. The basics of maintenance are easily forgotten.
> The basics of maintenance are easily forgotten.<p>Also undervalued by society as a whole and politicians especially.<p>They'd rather allocate funding for a new bridge they can point at and say "I did that" than properly fund the unsexy work of making sure the existing bridges are maintained.<p>Now apply that across most western democracies, repeat for decades and we are where we are.<p>The countries doing their vast infrastructure build outs will likely repeat the pattern in a few decades.
The other issue though is that with 24/7 connectivity, <i>any</i> unplanned downtime can feel like a major outage. 50 years ago there were lots of outages, to, but people didn't care as much, they just went outside.
50 years ago, an outage in Seattle didn't affect me in St. Louis as a rule. I'd go to the bank, hand the teller a check, they'd eyeball it, maybe hand me some cash, and process all the things on paper.<p>When banks started moving to computerized systems, maybe a bank would be unable to process something... but not multiple banks. I can't recall any "outages" that affected banks nationwide for any period of time. Walk into your local bank and find out they can't do something because their big system at the mothership is down? Perhaps.<p>Consolidation likely plays a part in this as well. I can't speak to the FAA/ATC systems 50 years ago, I have no recollection of what they were like then, but the only nationwide system I can think of around that era was Ma Bell. And I don't honestly recall any nationwide outages back then. Regional, sure. You might have a problem with part of the country getting calls if there was some kind of emergency... (e.g., everybody trying to call their grandmas in Kansas after reports of a tornado) but I don't remember there being any nation-wide problems like that.<p>We had to count on actual snow for snowdays. :-)
The manual processes don't exist anymore. If the IT is down, nothing can happen.
> And I don't honestly recall any nationwide outages back then<p>There was this one in 1990 [1], but it's notable because the system was otherwise very reliable. Also, this report says only 50% of call attempts failed, presumably most people would try their call a few times and likely get through.<p>[1] <a href="https://users.csc.calpoly.edu/~jdalbey/SWE/Papers/att_collapse.html" rel="nofollow">https://users.csc.calpoly.edu/~jdalbey/SWE/Papers/att_collap...</a>
I would also say that there are more single points of failure on the internet than there were 20 years ago.<p>In 2006, Amazon had just launched this new storage service called "S3." It would have struck people in 2006 as bizarre to think that AWS (and Cloudflare, and GCP, and friends) would one day be <i>so</i> crucial to the internet that a bug there could take down dozens or hundreds of companies.
50 years ago was 1976. Basically nobody had a computer at home. "Outages" were not a thing.
50 years ago my parents were getting power outages on the somewhat regular. I have had two in the last decade.
We still had a banking system, we still had phone lines, etc. But yes, the general lack of an expectation of always-on connectivity meant that service interruptions were much less of a big deal.
Anyone who hasn't embraced the 24/7 connectivity has been priced out.
Fifty years ago the store owner just wrote down your name and you could pay the bill next week.
One of the coolest things I've seen, system design wise, was working at libraries when the tech/power is out for a given period.<p>Every service except digital lending/materials continued to function, and there were fallback processes for recording everything that happened so the information could be added back into the digital system once the tech was fixed/power was restored. Specifically designed forms that were easy to use and easy to scan, an exact understanding of what needed to be recorded and why and where it would go later, etc. And a staff of people who were meticulous enough to actually follow through.
That isn’t something that has changed in the last 10 years.
I originally missed OP's comment about "a decade ago", but I don't think our "ability to get big things done" has changed in the last 10 years, nor the number of major outages.<p>When I hear people talk about "we can't do big things anymore" in the US, they are usually referring to mid 20th century stuff a la <a href="https://patrickcollison.com/fast" rel="nofollow">https://patrickcollison.com/fast</a>, not stuff that we did 10 years ago.
The topic of TFA and this thread is that these major outages appear to be happening more frequently this year - or in the last month - than we've seen in the past.<p>I do not believe the FAA has ever grounded the entire country due to a network upgrade going bad. So that is possibly an example of a hard thing we could do a decade ago, that we can't do now.
It may appear, but it's not.<p>> I do not believe the FAA has ever grounded the entire country due to a network upgrade going bad.<p>In 2023 the FAA grounded the entire country due to a faulty database update. So yeah, these things happen, people, like you, just forget about them.
Deciding on the ground stop instead of some other type of quick rollback might've been more to do with furthering financial agendas by making a scene (under the guise of "an abundance of caution" which does seem like a more popular thing lately than decades ago) as opposed to it actually being the only reasonable action.
No, that did not happen because every communication related to this is recorded, and will be audited in an investigation, and this would have been known to everyone ahead of time. Most likely the NSTB will investigate, though this has not been announced. There are also going to be congressional hearings and career civil-servants will be subpoenaed.
It doesn't seem hard to use two angle of attack sensors if you pitch the nose of a plane down based on its output.
The thing done today weren't even computationally possible a decade ago. The bar for competitive software is rising exponentially.
<i>> The thing done today weren't even computationally possible a decade ago.</i><p>Not the things that are breaking, no. The FAA was doing ATC a decade ago. We had email and cloud servers a decade ago. We had bank websites a decade ago. The scale of those things today is perhaps larger than a decade ago, but not enormously larger; indeed, the increase in scale in those things is much smaller than the increase in computing power in the world from a decade ago. So these things should have gotten more reliable--but they haven't.
Perhaps we would be better off if businesses simply couldn't get this big.
we skill-squeezed ourselves as an industry.<p>we made these systems simpler to maintain, to reduce the amount of skill we need to pay for to maintain them. And that does reduce the maintenance costs, at the cost of more compute. but who cares about compute costs where compute per unit of money doubles every 18 months, amirite?<p>unfortunately it also increases the competence required to change these systems without degrading their performance and usability.<p>since no one wants to pay that extra cost either, we let the systems degrade a little bit at every change instead, hoping they degrade slower than hardware improves.<p>that bet was bound to lose eventually, because of laws of physics, and because that degradation pattern affects hardware too.<p>and the double whammy is - with little demand for expertise - the supply is effectively gone too. so now that the walls have closed in, there is no way out.
We also had this decentralized network which turned into a monopolized shithole that fries normies brains. Although that was probably more than a decade ago.
Important stuff is the same. Banking doesn’t need fancy stuff
Both the FAA and the Microsoft services that failed have been around longer than a decade
I'm pretty sure I was able to do online banking a decade ago. USAA even had working 2FA at that time.
No we definitely had banking software in 2016.
We definitely did. And stuff like this happened back then too [1]. And even worse stuff before then [2].<p>[1]<a href="https://www.fintechfutures.com/baas/bt-fault-hits-uk-banks-digital-services" rel="nofollow">https://www.fintechfutures.com/baas/bt-fault-hits-uk-banks-d...</a><p>[2]<a href="https://abcnews.com/US/hackers-block-us-banks-online-service-bank-america/story?id=17343055" rel="nofollow">https://abcnews.com/US/hackers-block-us-banks-online-service...</a>
"Nothing existed before I was an adult" type vibes.
AI revisionism is out of control generally tbh lol
I've been working in software for 30 years. This is the largest collection of systems to be down at the same time in that period. I have been literally experiencing a degradation in online services over the last year or two. Its either poor quality AI generated code, or your generation is just incompetent. Your call...<p>If I were you (or was working at somewhere with an outage), even if it wasn't AI, I would still be blaming AI. Because the alternative means you shouldn't have a job in tech.
> The thing done today weren't even computationally possible a decade ago<p>I was able to log into my bank's website in the late 90s, FWIW. Yet today I can't seem to do that.
that's not really a good characterization. we have known this was a house of cards for decades. someone just turned on the fan.
[flagged]
>They aren't entirely wrong,<p>They <i>are</i> entirely wrong.<p>None of these outages, as far as we know, have a common cause. They just happened by coincidence inside the same news cycle.<p>Nor is there any evidence to blame them on AI, or tech layoffs, or hackers from Iran. It's more likely something boring and technical that doesn't fit into anyone's narrative.
My guess is a total disrespect for actually qualified people. You know, the ones that specialized in one thing, for their whole life. Every company tries to see how few people they can have and still run fine. And move fast. And no trainings. And no recognition for the people that could actually train other people. I think all these come together at some point and you get multiple catastrophic events in multiple industries.
If you have no skills it is hard to evaluate if someone you intended to hire has some.
Nailed it. Downward pressure on salaries, layoffs, outsourcing all drive technical excellence out of an organization. Then, when companies DO hire it's very hard to find competent people (and I mean find them at all, not find them at the cutrate you want to hire them at) and the people you do hire are just seat warmers
I would ask a few questions:<p>1. Does there seem to be a larger concentration of outages recently? (I would say yes.)<p>2. Is there actually a larger concentration of outages recently, or does it only seem that way because of an increased focus on this? (I would say that there is really a larger concentration, but I'm less certain about this.)<p>3. If there is actually a larger concentration of outages recently, is that because of AI? (This is the point at which I become pretty unsure either way.)<p>4. If it is because of AI, how exactly is AI causing this? (I think more widespread vulnerability discovery / exploitation is more likely than "everyone is vibecoding everything now and that's screwing everything up", but I'm not entirely sure.)<p>5. Is this just transitional growing pains, or is this a new normal, or is this the beginning phase of a pattern that is only going to accelerate? (I don't know the answer to this one at all! I hope it's the first thing, but I wish I were more confident.)
> They just happened by coincidence inside the same news cycle ... to blame them on AI, or tech layoffs, or hackers from Iran<p>I will add myself as another datapoint, yesterday, I investigated a reflection attack that was bringing an entire network down, the ip originated from both china and iran. While running my oss work: <a href="https://github.com/mickael-kerjean/filestash" rel="nofollow">https://github.com/mickael-kerjean/filestash</a>, over the last 2 weeks, I have received about 20 security reports when the usual rate is once every few months, and on top of that literally every single form coming on my website is being abused by spam, the rate of spam message coming through there has 100x increase over the last few weeks. I have never seen that much security work pushed over me ever
What evidence do you have that staff reduction is not at the root of some of this?
It could be some people rushing to get code into prod before the holiday freeze, or just a coincidence.<p>Either way, now that AI is more capable, you can really mess stuff up at scale.
The messing stuff up at scale is more because LLMs <i>aren't</i> capable, and people treat them as though they are.
Is this how the "AI will lead to the end of the world" type stuff I've been hearing about starts?
Code freezes for the holidays were several weeks ago. The code would have been deployed weeks ago too. And if AI writes better code than you, that says more about you than AI.
As history has shown again and again, blaming something only requires political will, not evidence.
The thing is, we don't know.<p>You saying they *are* entirely wrong is as baseless as their claim. Sure, you can say they don't have a common cause, and I agree with that, but chances of these events with different causes occurring so close together is very low and the chances of a same root cause is probably more plausible.
No, it all comes down to the decision-makers at the top being bad at their jobs.<p>One way or another, they've tried to avoid addressing tech debt, avoid hiring and retaining good people, and have more or less been kicking the can down the road / running on the edge without knowing it.<p>Or else they did embrace AI-driven "move fast and break things" approaches, and so they broke things.<p>They flip-flop between maximizing profits and draining operational divisions of any resources, and hoping to sprinkle a bunch of IBM magic pixie dust all over their infrastructure to solve all their problems without needing to understand any of it. You rarely find one that strives to understand problems deeply and invests in long-term planning and maintenance before a crisis hits.<p>The result is old systems that eventually break, system upgrades that go bad because nobody understands them, security holes that someone might have hacked into, etc. All the same basic root cause at the top, which is that most of our leadership class is full of incompetent short-sighted narcissists. And it "works" because most of the time it pumps the stock due to lower costs, and we only see the fraction of times that it causes headline-grabbing catastrophes. On a long enough timeline, though, they'll happily drive our entire society off a cliff--and we're getting closer and closer to that (at least politically).
I am assuming you don't have a direct line to each of these outages, and you have no proof that there is no common cause. A common cause could also be something like "poor production deployment practices" or "reliance on AI built software", in which case...<i>maybe they aren't entirely not wrong</i>.
It's extremely funny how many of your replies are proving your point exactly. One reply says "Yours is easy to hold since it can't have evidence" when it is simply stating that _there is no evidence of a claim_. Imagine that, "There's no proof of X" is somehow a magically unfair argument because it can never be proven! Wow! Nobody has ever thought of this before. Guess we have to assume there's inherently merit to X, then, and don't have to worry about actually constructing a proof of it (that requires patience and knowledge and first-party sources and does not get you internet points).
The boring news is that laying off 100th of thousands of IT workers because of a newly promised, never-seen-before technology, does indeed cause trouble. Who'd thought that these people did in fact create value?
Genuinely, what would it take for you to consider that it could, in fact, be the AI push?
Not trying to be that guy, but they do have a common cause: networked compute.<p>There are many more systems in the world outside of it, even if it is relatively ubiquitous at this point.
Where there's smoke...<p>"As far as we know" just indicates a lack of data, not evidence that they're not related. This is especially relevant for a political administration whose response to COVID was to bury their head in the sand by hiding data. Also: A public comment of "AI is hacking all our shit" wouldn't exactly calm the public.<p>It's fine to say, "I'll wait until we know more", but in the meantime AI progress continues and the sheer volume of cyber vulnerabilities it's uncovering is undeniable. It's not surprising that some state-sponsored bad actors would be use this as an opportunity to infiltrate too...
You also don't have any evidence that they <i>are</i> related.<p>In the absence of data, you are assigning blame to things you already hate, like AI or the administration. Motivated reasoning is highly prone to error, and it's a form of stupid-brained thinking.
Seems to me that most state sponsored bad actors would want to infiltrate in a less noisy way.
Well, digital centralisation and interdependency without fault hardening is a big problem. Just because it presents itself in slightly different ways across industries doesn't mean it is not a fundamental issue in our society.
None of the responses to your comment get to the heart of the issue. People believe these are likely interconnected because they no longer trust the authorities telling us they are not connected. I certainly don't trust the government, and the mainstream media seems unable to accurately cover such issues.
As a technical person, I tend to find it hard to dismiss as well. What's easier to explain. Someone said it in a comment, someone keeps pushing for the cheaper solution cloud infra was cheaper and now we see the cost of that.
I swear nothing works fine anymore, the world feels broken. Maybe those particular incidents are not interconnected directly but they are connected in the ether in the sense that everything is incredibly complicated and precarious.
It’s natural to turn to AI based development as one of the causes of the increase in large scale outages.<p>I prefer to ask a different question. Will all this AI development delivering us amazing new software? Are we just going to get 1000 free clones of Adobe Photoshop or can we expect some really exciting groundbreaking new tools?
Perhaps all the really clever use of AI development is in the pursuit of better AI and if that’s the case, why?
Yeah, I'd probably extend it to software too: which software actually delivers real value to society, and which is only created for software's own sake.<p>As to why, well economy must grow, no matter what.
It boils down to leadership. If all C-suite asks for is "more, faster and cheaper" then enshitiffication gets worse.<p>Unfortunately it will take many more outages for folks to realize that serious engineering talent has great value in the AI age. It's their judgement that helps speeding headfirst into building unreliable unmaintainable and difficult to extend systems.
I have a predication: In the next few years having any connection to the open Internet will come with massive risks. I.e. if you're not a government, military or $$$ company you won't be able to afford the steps it would take to harden said system against the onslaught from AI attacks.<p>Some other thoughts:<p>* Will the Internet become balkanised?<p>* These smaller networks will require a lot of personal information to even gain access.<p>* The return of the Sneakernet?
I'm as technical as most of us ... and I'm lightly suspicious ...<p>Not the same root cause of course, but there's something in the water
It is an interconnected problem, but it's the problem we're all already aware of. All these businesses and the FAA have gutted their operations teams. There's too much to do, and AI doesn't take less time.
they're interconnected in that we're all getting really overloaded by the workload created by AI, and even though we can use AI to get through the workload as well, we humans still have to be aware of everything flying by, and I think things are falling through the cracks more often. These days I work on ten or twenty issues at a time. it's a little nuts
Internetworking
software quality is going down in general<p>not sure if vibecoding is a cause or consequence, but it’s related, it requires as an axiom to stop caring about internals. And it seems to require disregard for quality too.
Basic competency is going down. Everything is outsourced such that no one knows how their critical systems work.
Competency going down, timelines being rushed, project managers and CTOs forcing new tools at breakneck speeds.<p>i'm all for experimentation and adding new tools when they're shown to actually help, but it seems like large software companies (especially banks and e-commerce) just don't care about quality anymore.
I think quality of most products is seemingly going down. To me it is a likely consequence consequence of increased financialization and money being expensive.
Contrary to "vibecoding" (which is increasingly becoming how anyone programs) being a cause or consequence, it'll probably be part of the solution.
I worry that this isn't the right metric for diagnosing whether there's a problem. I'd argue that we've had instances in the past where a massive increase in how accessible programming is ended up being a net gain in the long run for software even if the average quality went down (e.g., having computers move from giant room-sized mainframes that only companies and governments could afford to sitting in the living room on a table probably reduced the average quality because untrained amateurs could start write software even if they weren't skilled enough to be employed). I could potentially be convinced that this isn't the same and that it will end up being worse for software in the long run with a stronger argument, but "software quality is going down in general" isn't convincing enough evidence for me.<p>All of this is also downstream of what I think is even more important, which is what's better for society in general. Obviously low quality software is not better for society than high quality in a vaccuum, but I also don't think there's a single obvious objective answer for whether the influence of software on society is a net positive or negative today compared to, for example, when computers were all mainframes and all software was produced by people paid to write it. There are a lot of differences in society today compared to back then, and software certainly has some role in how we ended up here, but trying to attribute exactly what and how much is not an exact science.<p>This is a lot of words to basically say: if you're confident that this is a problem, I think it's important to state exactly why, since I think the interest parts of the discussion are in how you've concluded that.
Here's my “favorite” chart showing the steady decline in software quality over the last 25 years: <a href="https://trends.google.com/explore?q=%22something%20went%20wrong%22&date=all&geo=US" rel="nofollow">https://trends.google.com/explore?q=%22something%20went%20wr...</a>
Software quality peaked between XP SP2 and the victory in the market of node.
Very well put, your comment alone should probably be a dedicated post in here with people commenting on that timeline (people who were actually programming back then).<p>Maybe it was because I was a lot younger back then and a lot more idealistic, but especially for the ~2005 (i.e. just after the dot-com crash) - 2010 period (just before money would ruin everything in this industry) I can say that the programming bar was placed a lot, a lot higher compared to where I see it placed now. Software wasn't perfect back then, of course, but there was a real push (belief, maybe?) that with enough will and with enough new-knowledge-being-acquired then we (meaning all of us as an industry) will make things a lot better. In part the existence of this very forum is a simptom of that philosophy, what if it (originally, maybe it still is) being written in Arc, or Reddit originally being launched in Lisp.
Maybe node software was good initially, but its model was unsustainable, it relied on outsourcing to volunteer programmers, relying on such programmers means increased vulnerabilities, supply chain incidents, and low quality of software.<p>Vibecoding is an extension of the culture of overrelying on massive external dependency graphs. It's a preference for visual confirmation that something works and a disinterest in how it works. I think it's also related to the tendency of content feeds that are based on likes and swipes instead of searches, instead of specifying what we want, we are reduced to approving or dissaproving (until we are removed from the loop entirely)
considering how the experience with most SaaS products right now is insufferable with broken states and UI, I imagine the same broken behavior is leaking in every other area of product development, so I agree
Source = trust me bro. What’s that bias where things are so rare that when they happen it makes news, so you think they’re very common (eg plane crashes?).<p>Uptime and quality of software is about 10000x better than it was 10 years ago. Things just work all the time now.
Also, source = trust me bro? How can you make the opposite claim without backing it up either
> Uptime and quality of software is about 10000x better than it was 10 years ago<p>Extraordinary claims require extraordinary evidence. You're being the 'trust me bro' in this situation.
I'd argue that just illustrates the point that it's impossible to have an interesting discussion without a stronger claim from the parent comment. If I say something that's too vague to falsify, and you can just as plausibly claim the opposite, you're not at fault for failing to turn my claim into a more rigorous one.
Overall uptime is better than pre internet 9-5. It's so typical to become so used to technology that any disruption seems bad.
This misses that expectation versus reality is key to how a human experiences something. If it's 20 degrees F in November where I live (MI), I'm going to grumble and get about my life. If it's 20 degrees F in <i>July</i>, I'm going to be freaked out. The same situation (no access to banking outside of business hours) can have radically different context and communicate different things to onlookers. See the former USSR's reaction to seeing Swan Lake on TV in 1991.<p>The absence of something that once existed is not the same as that thing never having existed. A null entry and a non-existent entry aren't the same.
Yes, we should all stop complaining about unexplained technical interruptions in our infrastructure and go back to being grateful for every minute that my bank's website is open on the weekend.<p>/s
Any reason why it isn't the case?
Because there’s not one, shared cause between the outages. The lay person claims it must be AI, but that’s a bit meaningless.
The reason I say not entirely, is because there is kind of a shared cause. One way of looking at is is that the root cause is complexity, optimized for efficiency and speed rather than robustness. It's a feature of the economic superorganism we are operating as part of. See Joseph Tainter on Collapse of Complex Societies, the work of Nate Hagens, Schmachtenberger & Liv Boree talking about Moloch, etc.
Or put a bit more cynically, it is a symptom of a society-wide drift towards lower accountability and duty of care. It's a type of tragedy of the commons. Selfishness and externalized cost/risk means nobody optimizes for systemic reliability.<p>People "vibing" everything is just another component of this, not the root cause. Using AI tooling is just the new technique for what used to be called phoning it in, or going through the motions, or faking it until you make it.<p>Unfortunately, it's nearly always been an effective tactic for a selfish few. It's problematic when we don't have an equilibrium that keeps it in the minority...
Yes, that's how you take separate causes and transmorgify them into one omnicause, by muddying the waters until you can't see the differences anymore. Don't do that! It just adds confusion.<p>(The same thing happened with separate company's problems becoming "Big Tech." It didn't help.)
What does the "pro" person claim? That it's Iran?
I've heard claims that it's the people trying to get the US to fight Iran, recently unsuccessfully. Mossad is known for being very skilled. Not saying it necessarily is, but it goes back into the distrust of government angle. Trump saying he's fighting this war in Part for Israel doesn't help.
That there has never been an incentive to build quality software. As a result we spent 50 years building our society on top of poor quality software. We're paying for it now and will continue paying for it until the incentives change and quality becomes a focus.
I suspect there are incentives for Iran <i>not</i> to be identified as the culprit right now whether they are or not. If it <i>is</i> indeed Iran that would show they have the capability to do this and maybe the administration doesn't want that to get widely circulated. (and <i>if</i> it is a state actor it doesn't have to only be Iran - could be a coordinated effort - NK just did the big Binance heist and Russia can do this kind of stuff too)
NK's heist was against Binance, not Coinbase.<p>The main incentive for any nation state to avoid attribution to direct and material harm to many Americans is that they risk awakening American bloodlust. Americans are unhappy about the current Iran situation and wish it didn't start and that it would end already, but sufficient Iranian escalation would turn that around real quick and suddenly there are boots on the ground among other things.
From the other direction I could see that the administration wouldn't want to attribute incidents like this to Iran because it would just make Americans more unhappy that the administration decided to poke the hornet's nest when they really didn't need to. And like with not anticipating the closing of the SoH, they completely dropped the ball on cyberattacks as well.
That it’s a nuanced mess of factors. Like reality always is.
Maybe we're not looking far enough up the chain. Everyone used to use forums and other websites run by other people (eg Substack) to read and discuss about things they don't understand.<p>Now when people have a question, they ask AI, which is wrong a lot of the time.
Imagine a tree of relationships branching up to the very top labelled, "Because the Universe Exists" as being the root issue that relates <i>everything</i>.<p>Saying it's not related applies an assumption of what level of specificity <i>you</i> are thinking about. And that's how you quickly de-sync with other people, especially "lay people" who look at you funny when you claim there's just no way these things are related when it's hard to believe that based on experience alone.<p>As other comments suggest, it probably <i>is</i> related to an extent. Related by complexity of our Internet-based systems, related by age, related maybe even by enshittification of expertise, etc.<p>The further up the tree you find these relationships, the less specifically actionable they are (you cannot CVE enshittification), and the more they are about "what are the overall social/cultural/human issues we're grappling with in this era?"
Aviation got a whole lot safer when we started looking at the systems causes instead of the specific ways individual people, airlines, manufacturers screwed up. Ditto for anesthesiology, cars, etc.<p>Sure, focusing on individual small causes is helpful too, and it's a lot harder to do the higher and higher level system stuff. But, it can be done.<p>edit, P.S.: It's worth keeping a bare level of suspicions that there could be a common lower level cause, whether through inadvertent dependencies added or through hostile action.
To be fair, have there been post-mortems for any of them? Besides vague tweets or press statements?
> The lay person claims it must be AI, but that’s a bit meaningless.<p>Must be the water then
Is there?<p>Apparently the FAA outage was caused by the pressure to do things quickly, fueled by the AI urgency.<p>It feels like all the IT industry is feeling this pressure.
a) this is not known, there is no reliable data on either the FAA or new bank issue; and the information forthcoming from Microsoft may obscure primary causation<p>b) there is also a risk of sophistry and language games obscuring common sense truth<p>In the world where a state actor is engaging in active sabotage as part of a cyberwarfare effort, there is one shared cause.<p>Which exploits are responsible in each case may differ. Still one cause.<p>Do I think it's Iran?<p>No idea.<p>But the point is, none of us here have any idea at present.
I can see why people think it. I don’t think I remember a 7-day stretch like this…. ever?<p>- Massive Microsoft outage
- FAA ground stop
- Now this outage<p>Definitely a black swan at least? It’s not even the number of failures, it’s the scale.
It's true that we don't really know, and my first instincts lean toward hacking by a foreign government, but then I start thinking about media reports of shark attacks every summer. Shark attacks aren't unknown, but certain media channels like to pounce on them for ratings, and after a while to the average person it might seem like Sharknado. Stuff goes down all the time, but in this moment we're just extraordinary conscious of it.
One might argue that lazy sloppy work and the generally pathetic state of IT maintenance is the common cause.
My dad is a doctor. He keeps asking me similar questions.<p>I told him it's just like how he keeps telling his patients to watch what they eat, drink and smoke less, and get some exercise, but they don't, and then they have a heart attack and wonder why.
If an unfriendly foreign power were attempting to impose on America the insecure and unstable vibe-coded digital infrastructure we’re building today, we’d probably view it as an act of war.
Everything you said has been true for a long time, vibe coded or not. How much of the Internet proved to be exposed to a supply chain attack on node? That wasn't AI, that was just how things worked out.
Or the H-1Bs
Same with my parents, until I told them if FAA comms ran on teams and outlook we would have been boned a long time ago!
Maybe Jensen was what was keeping all of the nation's infrastructure running
There does seem to be a correlation with the fall in use of Substack and the frequency of these fuckups.
Not a bit occam razor's fan, eh ?
I’ve had people asking me if it’s Jensen Huang’s doing.<p>I guess for most “technology” is one big blurry mess.
Haha ask them how much they'd pay for fewer problems
Three massive outages in three business days in a row does seem like a pattern.
This is the obvious consequence of (failing to) replace software developers with AI slop. Despite the protests of the Antrhopic shareholders who dominate this site's comments, LLMs are hideously poor at designing software.
<i>My nontechnical co-workers see the Microsoft 365 outage, the FAA ground stop, and things like this as one interconnected problem.</i><p>Wait till they hear about United Airlines.
We (on HN) as generally technical people (despite the HNers who seem to think you can vibecode a NVidia competitor) that all of these incidents are unrelated with vastly different causes.<p>But I think there's an increasing consensus among "normies" like your coworkers who see these as related. They don't know why but assuring people they are unrelated fails in messaging terms when it <i>feels</i> related.<p>I think this will be an increasing problem where so much more code is not only written by AI but <i>reviewed</i> by AI. Things will slip through and companies won't be punished for these outages in terms of public perception (because it'll happen to everyone) or by the government. We just don't have serious consequences for corporate malfeasance or gross negligence. Like AFAICT the Sackler family should all die penniless in 6x8' grey prison cells.<p>Unfortunately we live in a country where the Sacklers get to stay billionaires while 1 year olds are shot dead at the behest of Walmart over a pack of diapers that weren't even stolen... with zero consequences [1].<p>It feels like this is just the next level of entshittification.<p>[1]: <a href="https://www.nbcnews.com/news/us-news/mississippi-ag-says-police-shooting-killed-1-year-old-was-justified-rcna604424" rel="nofollow">https://www.nbcnews.com/news/us-news/mississippi-ag-says-pol...</a>
Because they are. Trump just said that deranged democrat/antifa was cutting cables everywhere.
It is interconnected. Everyone bought the "cloud is up 24hrs" bullshit. My company had physical servers and we had 99% uptime because we had competent people. Profits are driving unsafe transitions, such is capitalism. Look at our crumbling old infrastructure and ask yourself why the "digital highway" would be any safer.
Honestly, I can't help but hope that ends up leading to enough popular support for more regulation for AI that something gets implemented. On the other hand, there's also ample historical precedent for hoping that a mass movement heading in the right direction ends up stopping at the point that feels reasonable and then being surprised when the momentum continues and people like me looking foolish for thinking that it wouldn't, so I might just be overly optimistic.
AI is not the cause of this kind of problem and it's regulation won't make it go away. Maybe it needs regulation, maybe it doesn't, but you're missing what's happening if you think that's what these widespread failures and vulnerabilities are about.<p>AI is acting as a sudden <i>precipitator</i> for problems that have been latent and growing for at least 15-20 years.<p>In pursuit of maximally rapid innovation and reduced capital expenditure, the software industry adopted a "move fast and break things" mentality <i>and</i> homogenized code and service infrastructure over a few winning cloud vendors, SaaS providers, and code solutions/frameworks/packages/etc.<p>The pitch was that you could rely on downstream experts to do better work than you could, that the biggest vendors and publishers had the best experts, that have them invest the capital would look better on your accounts, and that their scale would give you the best value for your investment.<p>The caveat is that effectively all technology products have serious faults lurking in them, even with the finest expertise working on them (not that most actually had that), and that when everybody homogenizes over the same providers and solution the industry shifts from a bubbling froth of localized bugs to a heavily correlated house of cards where widely correlated failures manifest in widespread collapse and catastrophe.<p>Whoops.<p>AI is acting as a breeze against the house of cards, but lots of things could have and would have and did, especially as it continued to inflate year over year.
If you're saying the parent comment I responded to wasn't talking about AI, what are you saying they were talking about? If you agree they were, why are you trying to correct me instead of them?
From experience, since the parent commenter didn't specify, I would take the "coworkers" as having a vague sense of dread and distrust with no real confident insight to the cause. They're likely to nod along to any explanation they hear from anyone they think is more technical or news-following than themselves, and then maybe repeat whatever last such they heard when chatting. With the occasional exception of politics, that's how most people approach technical topics outside of their expertise. I didn't guess what they might have in mind today at all, and didn't feel the need to.<p>But <i>you</i> did speak directly to AI, and specifically to advocate for regulation of it, which is why I replied to you. You were being specific and material in a way that the parent commenter was not, and that invited a different response.
I didn't specifically claim that it <i>was</i> the direct cause of this though, so you still decided to confront something I didn't claim over something the parent comment didn't claim
> With the occasional exception of politics, that's how most people approach technical topics outside of their expertise<p>You give other people way too much credit.
[dead]
[dead]
What's actually more likley are power grabs executed while the chaos is attracting all the attention. That's how we ended up with DHS.
I don't really see how regulation for AI helps. Companies were on this crash course of trusting Microsoft (or pick your other dependency that cant be eliminated as it is a monopoly or the minimum) to provide more and more of surrounding infrastructure. Until they had AI to run simulations of outside.competence there wasn't a snowball's chance in hell they were competent enough at IT to run someone else's infrastructure.
Across all of tech QA is the first thing you cut. When you’re doing your job right no one cares.
Man. When I joined $DAYJOB quite a few moons ago, I was so happy to see that we had an actual QA department staffed with smart and active testers.<p>All of them got laid off at the next layoff. That was before AI.
A few threads ago people are arguing with me about this.<p>Why have QA, every developer can simply QA and deploy, and talk to clients, and make sales calls.<p>Then again I don’t understand Capitalism. At a certain point these companies are so firmly entrenched they can ship buggy half working software. The consumer is effectively a hostage, all competitors are also delivering barely working products.
Why are consumers hostage? Why can't they switch to a better product?
Btw, not trying to say you are wrong with not understanding capitalism, I find it helps to view it not as an imperative but rather as a local optima in game theory. Capitalism just works really well for its own utility functions that it self dictates upon us.
Why stop there? Have them clean the bathrooms and mop the floors as well. A truly savvy business owner would have them do payroll and HR duties too. In fact, now that I'm thinking about it, just have one person do all the roles, imagine the money you'd save on staff.
I get your point, and largely agree with it.<p>At the same time, I’ve also thought I’d be much better off if my desk job required I spent an hour or two a day mopping floors, loading pallets, etc.
Of course, they were done testing!
i worked a pretty similar place to JPM, if qa was ever cut delivery times went up and people were okay with that for mission critical stuff. If you said 'this isn't tested well we're delaying' everyone would be okay with it.<p>on trading applications, and banking systems theres huge financial and legal consequences for cutting corners (look up knight capital). Pretty much the only way to get fired is to mess something like that up.<p>In some jurisdictions if you pushed a change that broke and it was flagged internally as not tested enough someone in the org would quite literally go to jail.
Unfortunately highly advanced tech people lack “selling skills”. Hopefully this changes with ai - prompt: summarize the work I’ve done and setup I’ve implemented and how it will help the company and why my role is extremely important.
nobody ever gets credit for fixing problems that never happened
That's 'loser thinking'! <a href="https://cybersecurityawards.com/journal/the-field/proton-loser-thinking-security-culture/" rel="nofollow">https://cybersecurityawards.com/journal/the-field/proton-los...</a>
Could it be related to <a href="https://news.ycombinator.com/item?id=50523300">https://news.ycombinator.com/item?id=50523300</a> ?
Only in the sense that WWIII has already started, and this is a cyberattack.<p>It's good that Iran, Russia, and North Korea are showing their teeth this early, when their attacks can be studied and counteracted.
West Coast, 3 out of 5 of these load for me no problem (I only use 3 of these services, cant check the others). Might be an east coast AWS thing? Can't seem to open a WireGuard tunnel into my home network on the east coast though, which is unusual. o_O
BOA and Chase both work for me on East Coast.<p>It's really hard for me to get a sense of how much outages are on the rise - versus every minor issue getting a lot of attention.
Having success with Chase on the East Coast as well at the moment. I'd like to know the actual scope of this as well. DownDetector as a source is kind of low value IMO, but the banks have released statements. Curious if these are actually a large issue since I don't have the opportunity to run into it myself.
You may be unable to actually perform changes. From my experience in companies, the main path homepage -> log in -> check balance was like literally 98% of all users, so those had some read only caches and backups that could be put into play for no downtime. But trading, moving money, etc. may still be down.
I can tunnel into the east coast from south africa at least. Doesn't touch AWS though.
Are you actually authenticating or just landing on main sites? The more public/marketing type pages are often hosted separately from the account platforms.
Coming so soon after the Office 365 debacle and the meltdown in the FAA network for air traffic control which caused the ground stop, it does raise the possibility of a targeted cyber attack being the root cause.
Or, perhaps there was some change in the IT workflow a while back, which causes an accumulation of technical debt, that is starting to make itself felt?<p>If it were an attack, it would be something that were more than annoying. The crypto theft by North Korea, for example, was obviously a bad actor, with a clear motive/benefit.<p>FAA incident also came like 1-2 days after a new system was rolled out, which would be quite a coincidence if it were not related.
It's possible, but if you were a state actor, why would you want to give the US advanced warning about your capabilities and give them a chance to fix their issues?
Maybe you're just script kiddies? Or grey-hats trying to expose and create incentives to prioritize/fund repair before worse things (e.g. digital attacks as acts of war) start to happen<p>But I don't know, I'm just someone with some minor experience larping in security who is spitballing :)
Only if you ignore all the information released by the FAA and Microsoft about those incidents.
They said "it's nothing cyber-related" whatever that's supposed to mean
Scuttlebutt on Twitter is that it's a compromised Optimizely script
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.
From the article: "...a technical issue at JPMorgan Chase caused ripple effects throughout the financial system."<p>Nobody is claiming multiple parallel failures. They are claiming one failure that impacted multiple organizations.
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.
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.<p>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.
Large outages are not a new thing.<p>People were making memes about the GitHub unicorn a decade ago.
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.
The crowdstrike outage was much much bigger, both in reach and in impact. It took days to weeks to recover from.
Remember when AWS messed up their BGP Routes?<p>edit: it was Facebook, not AWS
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.
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).<p>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. With everybody swinging for the fences and the median blast radius increasing and the checks/roadbumps eliminated you end up with a lot of incidents because the total number of merges and the size of the diff has increased by quite a bit per sprint.
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.<p>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.
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.
Or maybe that cyber attacks are generally known after the fact that they are cyber attacks via things like extortion.<p>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.<p>Like if we learn that PII was stolen, then it's be safe to say that this was a cyber attack.
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.
That's just a strawman argument.<p>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.
blaming this problem to vibe coding != ai bad at code<p>shit programmers have always been a thing, these same shit programmers now putting output from claude straight to production<p>on top of this there are literally PMs getting involved and doing their own PRs, see vscode recently
> Because people want to believe that AI code is inferior<p>No, people want to believe that it is good, <i>despite all evidence.</i> 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.
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.
I find it fascinating that anyone thinks computer programs will be different than anything else.<p>Clothes. Food. Appliances. Tools. Electronics.<p>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.<p>Why would coding be different?
if only...
>Because people want to believe that AI code is inferior,<p>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.<p>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
yes, I read some java today where I wished for the clankerd to have done it...<p>Think system(curl) and random-if-cascades which are never reached - they removed the system(python) in this iteration though...<p>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.
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.
Just like humans, it varies wildly. Stating anything other than that is speculation at best.
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.
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.
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?
Except human code is reviewable at a reasonable speed
Before laying off half of my company the last place I worked fired QA first
The initial postmortums are out already for the 2 previous event, and they appear to have nothing to do with vulnerability.
I don't think the average person cares tbh.<p>It's caused my AI, it doesn't really matter who's fault it is
The companies in question have confirmed it wasn't due to cyber attacks. That's why.<p>What's it going to take for the AI pushers to see that maybe this isn't the road to go down.
> AI vibe coding<p>What's new? What has been operating fine until the AI, cloud, and centralized computing came onto the scene?
I'd assume that whatever happened affected a single centralized service that these banks all relied upon.
Like everything else it’s probably a combination of both (as well as other causes).
Everyone is vibe coding now. It's not just you. It's not an assumption.<p>Vibe coding, vibe reviewing, vibe fixing. No one has a clue how software works anymore.
"AI cannot fail, you can only fail at AI".<p>Somehow I knew I would find something like this on this comment section.
Why can't it be both?
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.<p>My first thought for this week's outages has been that people are moving too fast and are, as the saying goes, breaking things.
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.<p>Basically, blaming AI slop supports a lot of pre-existing beliefs, while blaming AI hackers does not.
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.
[dead]
Hanlons razor. “Never attribute to malice that which is adequately explained by stupidity.”
Presumably this must be the "best" time for phishing/fraud ?
It's never a bad idea to carry a few dollars in case of a payment processing problem.
From Microsoft to the FAA to Chase.
The MTBF singularity is the one I'm concerned about.
What did MS say caused the Office 365 downtime?
To see what's next, let's turn to prediction markets!
Just used my Chase card at Walmart. Worked fine.
This appears it could to be related to the compromise of Optimizely, I see tags related to it on Wells Fargo's home page
takes me back to the 90's...<p>"on a long enough timeline the survival rate for everyone drops to zero"
Logged into my account at all four of those banks just fine, even submitted payments.
Is Zelle the commonality for this outage? All of those banks work for me, but I have been careful to never enable Zelle on any accounts.
Have been getting some core.finicity.shared.noAccountAvailable.instruction errors with Capital One when trying to connect back accounts
companies relying on a single cloud (Azure) for mission critical workloads is a big problem
Im having GCP problems. Anyone else?
Just checked with my Chase account. It's fine. Was able to login via the mobile and web app.
I have feelings foreign entities gave there hands on this
Is there a 'wikipedia' of outages anywhere? Something more like a database.<p>Cloud outages, infrastructure outages, transport disruption, significant websites going offline etc.
“Life can change in a blink.”<p>- Nathaniel Rothschild
Nov 5, 2026
America is melting
The businessmen and entrepreneurs have full control of the country. We're cooked.
To be expected from the 'melting pot', I suppose
I kinda expected things like this to happen the week of the Anthropic IP0. EA sees everything as a trolley problem anf tries to create them wherever they can. Thwy will mess with critical infra to get themselves the regulation they want.
Did anyone have Spamhaus put them on their spam list within the last week for not putting the proper HELO?<p>Ours was misconfigured as ourdomain.com instead of mailserver.ourdomain.com<p>Here's their announcement:
<a href="https://www.spamhaus.org/resource-hub/deliverability/spamhaus-sender-guidelines/" rel="nofollow">https://www.spamhaus.org/resource-hub/deliverability/spamhau...</a>
Hmm, Apple pay didn't work for me this morning, but Paypal (with a CC) did.
Went into a branch and they couldn't help me!
In past week i have heard about lot's of outages.
There's going to be a big swing to get off the cloud methinks, hopefully it benefits my career
I reckon, it would take 3 days of full outage for an average company to even consider the work needed to migrate from cloud providers or services. Obviously with some exceptions around risk to life systems, which should have an independent disaster recovery plan already.<p>M365 would have needed to be down for a full work week for job adverts to go out for an internal IT infrastructure team.
I doubt it, c-suite will never approve the spike capital expenditure for buying hardware now they're under a nice smooth subscription curve which doesn't harm their profits as dramatically.
Hows the cloud responsible for the outages in a way that is mitigated by self hosting in recent outages and this one?
Not needing to run at big tech scale makes self hosting easier.<p>You also have full control of downtime and recovery rather the refreshing the MSFT status page.
Presumably a central provider takes down your dependent services with no local ability to navigate around the outage. Removing the dependency obviates the outage risk. It introduces its own downsides as well, but that's a different discussion.
USAA also appears to be down, at least for me.
I was able to login and check my account balance
I asked Claude to log in to everyone's accounts and check on them. Don't worry, it had no trouble getting in and it says everything is fine.
Yes, it's sad these systems are going down all the time, but if we wanted them to stay up we'd have to pay the people who maintain them, which means less money for the stockholders. So you see, our hands are tied.
I love how trusting everyone is after three major outages on consecutive business days, hot on the heels of months of warnings and demonstrations of AI enabled attacks, that these aren’t attacks, solely because people incentivised to say that everything is normal are saying everything is normal.
I'm a little surprised I didn't learn about this outage from Flavor Flav [1]<p>[1] <a href="https://www.mediaite.com/media/weird/flavor-flav-more-than-on-time-when-it-came-to-news-of-faa-grounding-flights/" rel="nofollow">https://www.mediaite.com/media/weird/flavor-flav-more-than-o...</a>
All of the project managers running large-scale production systems with Claude Code are having a rough go of it lately.
Whole lotta people in this thread blaming these outages on whatever their personal software industry bugbear is with zero evidence.
So glad that coding has been solved.
They, too, didn't need programmers any longer and let AI take the wheel?<p>The thing is, even if true, they'll never admit it. People who make these kinds of mistakes (if this is what it is) are also not very prone to honest bouts of introspection either.
Honest bouts of introspection aren't necessary to keep the line going up.<p>So, your company shit the bed due to your plans. So what? You went to the right school and have some experience in the c-suite. You probably have enough money to go a decade without cleaning out your savings.<p>Break down the company for scrap, file an IPO for the good parts, whatever. You'll make the money back.
Outage at SEELE you say ? Does NERV know ?
Chase web services aren't down...
Wow, I wonder if there is an underlying cause.
Its WWIII<p>Reuters, March 26, 2025
EU tells the public to hold 72 hours of emergency supplies.<p>_<p>The Guardian, March 26, 2025
Stockpile 72 hours of supplies in case of disaster or attack, EU tells citizens.<p>_<p>The Guardian, October 23, 2026
Tinned mackerel, hand-crank radios and bags for poo: crisis-prepping guides around the world.<p>It list government preparedness guidance from the United Kingdom, France, Germany, the United States, Finland, Sweden, Norway, Denmark, Australia and India.
If I had any money in the bank, I'd be worried. Fortunately, I'm tapped out now :|
Thursday: MS 365
Friday: FAA
Monday: banks
Wednesday: Anthropic IPO
AI fearmongeeing post to boost stocks along with comments to corroborate.
We are under attack and the enemy is incompetence or actual terrorists.<p>They would/will never admit it is AI breaking everything either.
Aw man just begrudgingly switched to them
The US has no natsec currently due to its leadership. There has been an intentional purging of those with real expertise at the topmost layers. Mass layoffs of experienced folks. AI use rise and all that entails. Several billionaires with motive and resources to do sabotage or cause chaos. Now add the US attacks on Iran giving huge motives for the latter to push whatever buttons they can. One could argue we should be surprised 2026 hasn't been much worse than it has been. And there are reasons to expect it to worsen much more before it can ever get better.
Queue the "It's Biden's fault" excuse in 3,2,1 ...
"according to the website downdetector.com"<p>Ugh. DownDetector's methodology is… not great.<p>Steam isn't down: <a href="https://downdetector.com/status/steam/" rel="nofollow">https://downdetector.com/status/steam/</a><p>Amex isn't down: <a href="https://downdetector.com/status/americanexpress/" rel="nofollow">https://downdetector.com/status/americanexpress/</a><p>Visa isn't down: <a href="https://downdetector.com/status/visa/" rel="nofollow">https://downdetector.com/status/visa/</a><p>AWS isn't down: <a href="https://downdetector.com/status/aws-amazon-web-services/" rel="nofollow">https://downdetector.com/status/aws-amazon-web-services/</a><p>But each has a huge corresponding spike there.
DownDetector's methodology is fine, it's just noisy. The way to use it is to look at the top-reported failing sites in the ranked list on their homepage, which has been the correct root cause for every major outage I've seen. Ignore the lower ranked ones.
How do you know some of these aren't experiencing a partial outage? Responding instantly to partial outages that never get reported on status pages seems to be one of DownDetector's biggest strength.
> How do you know some of these aren't experiencing a partial outage?<p>Is there <i>any</i> other sign they are? That Google, AWS, Steam, Amex, Visa, etc. are <i>all</i> simultaneously having significant outages right now?<p>> Responding instantly to partial outages that never get reported on status pages seems to be one of DownDetector's biggest strength.<p>I've predicted all fifty of the last one recessions.
I live close (as the fiber flies) to one of the more popular AWS datacenters so I have no doubt that there could be situations where I can access sites that others can't, or in the case of a proper AWS cockup, where I can't but many of you can.<p>And when it's not DNS (it's always DNS), it kind of depends on how load redistribution works. At some point I have to switch to load shedding, and so Idaho and Montana might just be shit out of luck.<p>If the NYC office is still able to do work, I don't want the Denver and Chicago office to overload their servers and now nobody can get any work done.
Payment not working could be considered a partial outage.
> I've predicted all fifty of the last one recessions.<p>Meh. I've come to the realization that the answer to the question "is X service up or down right now" <i>is</i> as fuzzy as forecasting the weather or predicting recessions. With giant distributed systems it's always half-down in some unique way. Especially so for anything with a dependency on Microsoft services.
Also happened last week during the Outlook outage. It showed the entire internet down for some reason.
I always think of the time the company that acquired us put our Wiki and (some of) production storage on the same drive array and when it failed we couldn't access our runbooks. Lots of anger lines coming off of people who are permanently grumpy the rest of the time. Like people too angry to trust themselves to talk, so one word answers.<p>After that our operations team got most of its autonomy back.<p>How do you make an app that watches everyone else's infrastructure but can't be taken out by a common cause?
i see this comment on every single "its down" post, it's not a useful comment- it is down, Chase is partially working.
The article cites a Chase rep saying <i>they</i> are impacted by a bug of some kind.<p>The article writer then went to DownDetector and wrote a headline "Outages reported at Bank of America, Chase, U.S. Bank, Wells Fargo and Zelle" based on just that. As far as I can tell, there's zero genuine evidence for that.
I’m experiencing degraded AWS ECS service today so it’s atleast a bit helpful. AWS is probably never going to be down accross all regions and all services 100%.
Isn't it just based on user reports? What explains the spike in user reported issues in those services recently?
> Isn't it just based on user reports?<p>DownDetector considers someone looking up "is Visa down?" a report, even if it isn't.<p>Click my links and it contributes to those "reports".<p>One provider has a major issue, and people go there and click into non-down companies, which is seen as a spike.
Is there a problem with that? Do normal people google "is Visa down?" if they don't think Visa is down?<p>On the other side, does a user google "is Visa down?" going to a website and clicking "yes I think visa is down" any better?
> Do normal people google "is Visa down?"<p>Normal people Google "is Chase down?", find DownDetector, and click it. (Note that the article has a Chase rep quoted saying they do indeed have an outage, and none from other companies.)<p>Some of them then click into the DownDetector home page and browse around. Suddenly <i>everything</i> is spiking.<p>Every time I've seen any one major company with issues, DownDetector has spiked across the board. As it is now. Google and Amazon are apparently down.
> DownDetector considers someone looking up "is Visa down?" a report, even if it isn't. Click my links and it contributes to those "reports".<p>Really? It seems to me you have to click a specific aspect of the service to report as down once you land on that page to report an outage.
I assume their methodology weights active reports higher than the implicit ones.
<a href="https://downdetector.com/methodology/" rel="nofollow">https://downdetector.com/methodology/</a><p>> We process tens of millions of problem reports each month and cover over 36,000 services in 72 countries.<p>Ask a few normies if they know what it is, let alone have filed a report.<p><a href="https://downdetector.com/about-us/" rel="nofollow">https://downdetector.com/about-us/</a><p>> Downdetector collects reports from users <i>and monitors other online sources for service issues.</i><p>Or look at the comments on any of the pages. "My card declined"; "18yr femboy down for DM".
<a href="https://news.ycombinator.com/item?id=50521819">https://news.ycombinator.com/item?id=50521819</a>
Has downdetector ever been down?!
I can't comment on the others, but Steam and Amex were both partially down earlier this morning.
I mean, if Visa/Amex transactions are not working because their bank is down, end users don't know the difference. Card says "Visa" on it, card is not working, end user blames Visa.<p>Steam/AWS, I got nothing.
[dead]
[dead]
[dead]
[dead]
“Life can change in a blink”<p>- Nathaniel, Rothschild
Nov 5, 2026
Its so much easier to generate code with genAI though.
The degradation in software quality across the board (Spotify, Google Maps, GitHub, YouTube - to name a few) has been very noticeable for me, and I suspect AI has a lot to do with this.<p>The thing is - I also think AI can be used to build very high quality software. The problem, I think, is that the typical big tech/VC tech/MBA tech type company (who control most proprietary software at this point) have very little incentive to actually care about quality, and that was quite obvious even before AI.
I remember before I started using AI (I was pretty late to the game), I assumed all the bugs and instability were because people were writing software with AI. Now that I've seen how good the code that AI writes can be (CAN be), I'm moving more to the thinking that it's from AI being used to find vulnerabilities.
I've never had AI one-shot even a 10 line script that I didn't manually revise. To be fair, it usually produces something that works, but after seeing it I'll realize that my prompt was too vague or I left out some edge case. So it's the old problem with software "it does what was asked for but not what was needed."<p>So I speculate that a lot of problems with AI code are just that it is accepted uncritically because it builds and doesn't have any syntax errors.
There’s a pressure to deliver more and faster from management. So instead of using LLM to reduce the coding time and allocate more time for review, everything is scaled down and there’s even less time for review. And you’re responsible for more as teams are also scaled down.<p>Not really a great recipe for good code.
It’s more that management pushes more output and with AI it’s very easy to achieve but that will create slop.
I think majority of companies don't know how to build safely with AI. It's just kind of handed off to engineering and mostly used as one-off chat interaction to get stuff done. Very few are building any kind of harnesses around SDLC that focus on architecture, testing, security and etc. I think we'll get there at some point, but in my experience the smaller tech players are just now on-boarding to use AI in general in any kind of capacity. We're not talking about best practices yet.
Wondering if this has anything to do with the QA function being folded into the dev team in the last 15 years or so.<p>I always defended this, but it appears maybe we don’t have enough developers that take pride in the work they ship. LLM coding made this pretty obvious.
It’s not lack of pride. It’s because they can’t say: “ok development is done, now I need a few days to thoroughly test this”.
Engineers don't really decide what gets shipped at a typical tech company, you either ship trash when the marketing/MBA/'strategy' NPC says or they'll find someone else who will.
> I also think AI can be used to build very high quality software.<p>I don't, and I think your comment is rhetorically useless because you've been bullied into making this ridiculous concession.
IMHO the only way to build good things is to pay attention to the details. And coding agents, while greatly increasing the <i>appearance</i> of productivity, they are causing people to pay less attention to what they're actually producing. This is the inevitable and obvious result.<p>Agentic coding <i>could</i> be a world-changing benefit, but the current way it's being sold and used as as a cost cutting measure -- produce software faster than ever before with fewer software engineers! Get rid of those pesky experts!
We're in the v1 machines screws stage where everything is worse but with a clear path to get better .... I hope
It isn't a software or tool problem.<p>It is a C-level executive problem. With the FAA it is the agency directorship problem. Same issue.<p>These people, very literally, are trying to run the world with power point presentations and executive summaries drafted by sycophants. 70 years ago these people had actual experience doing actual work and trying to grow businesses and doing stuff at the ground level. Now they are given their positions through a combination of credentials, connections, and political maneuvering. None of which actually relates to how well they can or cannot run a organization.<p>When reality disagrees with what they get in their emails and presentations then it reality that is wrong. It is the messengers that are the problem, not their competency.<p>This is nothing new. But the failures in leadership compound over time, like interest to a unpaid debt. They start off with healthy growing companies and thanks to government protections and bailouts it takes decades to for these organizations to decay into total dysfunction. In the past these sorts of people would be removed and their assets reallocated to competent management through bankruptcy and competition. However that natural process is not allowed anymore.<p>All AI is doing is handing them more foot-guns.<p>They think they can do better/faster/stronger/cheaper with AI and if AI causes problems then it can just be fixed by paying for better AI. Which they assume is just right around the corner, always.<p>Just wait until they start to realize that it is
Very well put, and I think (open) AI will help competent people outcompete these clowns, which is what makes me optimistic. AI is a multiplier, but multiplying bullshit just creates more bullshit. These people are far more replaceable than competent engineers, even more so with AI.
broken windows
Part of being sane is accepting that some tools, while being very powerful, are too easily misused to be widely distributed to those lacking proper training. This is why you cannot just go and buy 5 kilos of azithromycin
Ehh I don't really buy that. Who decides what tools are distributed to who and how?<p>Don't want to get into a political debate here but I'll say that I think that open AI models and access to them is a benefit to society, while closed, proprietary models, controlled by tech billionaires are probably net bad for society.
> some tools, while being very powerful, are too easily misused to be widely distributed to those lacking proper training.<p>Could you define 'proper training'?
I've endured plenty of fucked-up shit from so-called 'professionals/ experts/ trained people' over the last 30 years or so.<p>I'm currently assisting a couple of vibe-coders improve their 'too easily misused...[and] widely distributed' (available on their sites, or github) tools - I mean slop - that benefit me in ways traditional companies have no interest in.
And the updates are fast (daily, mostly) and accurate because, unlike jeremy with a pretty CS degree and a nice job, these people actually give a crap' and don't have a manager to say 'you can't do that'.
Also part of being sane is accepting that the cat is out of the bag and big $oftware/ tool manufacturer better get a move on.
Disclosure: my interests are not critical to anything; quite the opposite, but people are learning faster and faster with Ai learning faster and faster.
Who needs azithromycin if a series 1's and 0's can accomplish so much more?
For good or bad.
No, i cannot. If i could, i would be proposing concrete ideas. But I also understand why I cannot buy 3 kilos of plutonium or 5 kilos of antibiotics, and understand the modern ML models can do just as much damage while being more available.
Software is solved!
Crypto blockchains such as Solana, Tempo and XRP are still up and running while the banks are down and you have no choice but to wait for them.<p>What a disaster.
[flagged]
incredibly misinformed take - llms are undoubtedly performing real work. it's true that the rate of production of bad quality code has skyrocketed, but there are certainly teams that are increasingly productive and systems that are increasingly more secure because of them
For example...
> but there are certainly teams that are increasingly productive and systems that are increasingly more secure because of them<p>I don't take your assertion of certainty seriously. In my opinion, you are not qualified to evaluate the quality or security of code. You are looking at a series of related disasters and shouting that nothing is wrong. Please forgive me for not taking your perspective seriously.
It's a tired discussion. LLM generated code can be awful, but it can also be very good. If you think all LLM generated code is bad, you haven't used any in the last year.<p>Company process and how LMS are treated in the development process is actually of interest. Are they YOLO shipping code or are they reviewing it and using LLMs as a tool, instead of a replacement for an engineer? That is where LLMs bring danger.
> If you think all LLM generated code is bad, you haven't used any in the last year.<p>I use Opus 5.5 and it can't generate code anywhere near as good as mine. I'm not an exceptional programmer either, I'm fairly middle of the road. LLMs remain bad at programming, despite the claims of AI bros that only within the last 6 months have models become good (which they curiously have claimed constantly for years).
I think they’re pretty clearly not designed by idiots. A lot of smart people work there.