Curious nobody allows for the possibility this all comes as result of some adversarial action on behalf of … potentially so many actors, and given the recent streak and stream of CVEs discovered with help of LLMs.

So my bet is if this is in any way AI related - perhaps the reasoning should go the other way around and is not mere dumbness of otherwise great company everyone’s buying like crazy for years now. Even my diehard Apple fans friends own MS stock.

▲

mmillin 15 hours ago | parent | next [-]

For what it’s worth, the latest status updates from Microsoft address this concern: “At this time, we have no evidence of malicious activity associated with this incident.”

Abscence of evidence vs evidence of absence notwithstanding, it’s probably best not to overly speculate.

▲

jkkola 14 hours ago | parent [-]

I think the "at this time" is important, they were probably more focused on bringing everything back rather than doing a full investigation. I'm curious about the post mortem.

	▲	tremon 12 hours ago \| parent [-]
		Microsoft employs enough people that they can afford to have one team scan for unusual ingress/egress traffic patterns while others work on troubleshooting. If not, they should not be shedding 60k employees right now.

▲

philipwhiuk 16 hours ago | parent | prev | next [-]

> Curious nobody allows for the possibility this all comes as result of some adversarial action on behalf of … potentially so many actors, and given the recent streak and stream of CVEs discovered with help of LLMs.

Occam's razor.

▲

jasonvorhe 11 hours ago | parent | prev | next [-]

Blaming every outage on some evil AI aggressor isn't helping. It's just more FUD.

▲

jasonvorhe 14 hours ago | parent | prev [-]

Looking at MS' track record I'm confused why anyone would assume a malicious 3rd party first while Microsoft has been "trying to turn it off and on" again for hours.