Major Microsoft Outage

[Carth]

Originally Posted by Jaymoss

Where did you buy your blinkers?

Can you tell me categorically that this is all just coincidence ? if you answer no to that then you do not know if what I have said has happened or not. Your belief that I am being paranoid is just that with no proof to back it up

Just my opinion here:
Governments are looking at the state of play in certain areas and don't see things improving in the near future.
It's quite likely that shortages ,both in food, and materials, will get worse over time, especially given the weather we've had and what is forecast yet to arrive.
The big tech boys are pushing AI and data centers and there's a lot of stupid money involved - money lost or gained we don't know yet - but the fear is if it's not pushed on with they'll fall behind in the race.
We've already had examples of what could possibly be AI causing disruption by not integrating correctly with older technology, or in fact overloading older systems etc. We've also had the 'hacking' of supermarket freezers etc. and the threat of this becoming worse is there.
The recent instances of tech 'falling over' and infrastructure failing (water/power) is probably more to do with a lack of funding for upgrades and improvements than anything else, and probably coincidence when, given the age of the 'components', a few things go wrong in the same time frame.

Governments can either make people aware they may need to stock up on essentials, or they could just keep quiet and hope nothing happens.

[Jaymoss]

Can you not see that current events could all be linked? The warning M$ going down Air traffic control going down. The risk of cyber crime has never been higher because you can create a virus just by paying a subscription to an AI model now without any code knowledge.


How do we know what we are being told is the truth ?

"The cause was aging analog air traffic control routers and switches that became overloaded with data after new technology was introduced into the system. "

"Microsoft says the cause was a network configuration change introduced during an earlier network capacity upgrade, which surfaced after a recent network change. Specifically, a core process responsible for establishing secure connections (authentication/routing) became overwhelmed, causing servers to fail automated health checks and drop out of rotation — triggering a cascading capacity degradation across the platform."

I am not buying either explanation

[papa smurf]

hmm sounds like the laggy band snapped

[Jaymoss]

Originally Posted by papa smurf

hmm sounds like the laggy band snapped

Can you not see ? both the reasons are almost identical.

[Carth]

Originally Posted by Jaymoss

Can you not see ? both the reasons are almost identical.

They do appear to be yes, pushing aging equipment past their operating parameters?

[Jaymoss]

Originally Posted by Carth

They do appear to be yes, pushing aging equipment past their operating parameters?

So 2 newly upgraded systems fail at the same time both causing massive disruption . That is one hell of a coincidence all happening within a short period of time warning of this very thing but worse

[Sirius]

Originally Posted by papa smurf

put's tin foil on shopping list

Here is advice on how to use your new hat.


https://www.youtube.com/watch?v=wFNO...&start_radio=1

[Dude111]

I dont think really want us to know what really happend!!

[Carth]

Originally Posted by Jaymoss

So 2 newly upgraded systems fail at the same time both causing massive disruption . That is one hell of a coincidence all happening within a short period of time warning of this very thing but worse

Both older systems apparently having been configured (probably the wrong word) to work alongside/with state of the art AI enhancements . . . as I said, probably pushing the envelope.

In the same way I'm guessing that connecting an electric cooker to the fusebox with speaker wire tends to cause issues

[Sirius]

Originally Posted by Jaymoss

So 2 newly upgraded systems fail at the same time both causing massive disruption . That is one hell of a coincidence all happening within a short period of time warning of this very thing but worse

That is an absolute classic IT nightmare scenario—often referred to in the trenches as a "resume-from-off failure." When enterprise or core networking gear runs continuously for years, the electrolytic capacitors quietly dry out, lose their capacitance, and develop high Equivalent Series Resistance (ESR) under constant thermal stress.

As long as they stay powered on, they just barely limp along. But the moment you cut power for maintenance or a rack move, the dielectric fails completely. When you try to cold-boot them, the inrush current fries them—and if you throw a fresh firmware update into that mix during the reboot sequence, the whole world sets on fire

Company's tend to run systems way past the EOL now to cut costs, then it bites them on the arse

[Jaymoss]

Originally Posted by Sirius

That is an absolute classic IT nightmare scenario—often referred to in the trenches as a "resume-from-off failure." When enterprise or core networking gear runs continuously for years, the electrolytic capacitors quietly dry out, lose their capacitance, and develop high Equivalent Series Resistance (ESR) under constant thermal stress.

As long as they stay powered on, they just barely limp along. But the moment you cut power for maintenance or a rack move, the dielectric fails completely. When you try to cold-boot them, the inrush current fries them—and if you throw a fresh firmware update into that mix during the reboot sequence, the whole world sets on fire

Company's tend to run systems way past the EOL now to cut costs, then it bites them on the arse

I accept all that but for 2 systems to crash at the same time for the same thing after we the warning about systems going down is a lot to swallow for me anyway

Originally Posted by Jaymoss

I accept all that but for 2 systems to crash at the same time for the same thing after we the warning about systems going down is a lot to swallow for me anyway

As the saying goes, "shit happens".

System crashes are not uncommon, and in this case, it seems a domino effect came into play.
One failure pushed the load onto others, which then failed under the extra load, and so on - its not as rare as you may think.

I've seen entire telephone exchanges fail because one thing failed, which led to another overloading and failing, and bang, it all falls over.

[Sirius]

Originally Posted by Paul

As the saying goes, "shit happens".

System crashes are not uncommon, and in this case, it seems a domino effect came into play.
One failure pushed the load onto others, which then failed under the extra load, and so on - its not as rare as you may think.

I've seen entire telephone exchanges fail because one thing failed, which led to another overloading and failing, and bang, it all falls over.

The old cascade effect, i was involved in the recovery from one many moons ago.

I was involved in three failures/isolations, two with TXE4, one with System X.

IIRC, one of the TXE4 failures was a cascade effect (Pulse genny and something else).
I was in the exchange at the time as we saw the affected systems going offline one by one.

The other was two failures which combined and caused the exchange to isolate, the chances of that are very remote.
I was in the another exchange (close by) at the time, we got called over to help get it online again.

The system X failure caused all the remote concentrators to be isolated from each other, I dont recall what caused that.
I was in one of the remote exchanges at the time, you could call other lines locally, but not any other exchanges.

None were fun at the time, but no one got their foil hats out.