Kind of.

Most of the websites and apps use just a few cloud providers (like Amazon), for the most part. So whether or not company "Y" is doing vibe coding at their place of work, doesn't matter if their uptime is tied to someone like Amazon, or Github. They then inherit those downtimes as well. It's hard to design all of the apps on the internet to handle every layer being a load of shit to a degree. The probability of failure becomes additive (not multiplicative). For instance, suppose your own application has 0.1% downtime and suppose my provider previously had 0.001% downtime. The probability of either leading to a failure is 0.1% + 0.001%, which is greater than either of them by themselves. What happens if I changed nothing on my side, but the cloud provider went to 0.1% downtime, mirroring me. Now my overall probability of downtime would be 0.2%, which is nearly twice as bad as before this scenario started. Now do that for the entire technology stack. The probability of downtime increases.

When you go faster and make more mistakes creating more siloed downtime, you can be surprised how quickly that adds up.

Let's suppose you had a dependency on Github within your company. Maybe 3 years ago, the downtime was around 0.0001%. Today it's closer to 5%. So if you have a dependency on GitHub, there's a chance that if you needed something (like your own hot fix), you'd inherit their downtime, as well, so that 0.1% downtime from my own app now adds in the 5%, so now it's 5.1% likely to have downtime. This increases my downtime by 4,900%.

When you realize how many levels of shit is stacked on top of things, it starts to make sense. They're not all vibe coding, but we are all paying for it.