[bobbob1921]

How is this “another” Microsoft outage? I assume the first outage the article is referring to was the crowdstrike issue (not a Microsoft caused issue). Or perhaps I’m not aware of a different non-crowdstrike Microsoft outage recently?

[hughesjj]

The day before crowdstrike a bunch of Azure services were down in us-central-1 and devops was down globally AFAIK

https://news.ycombinator.com/item?id=41000822

[raxxorraxor]

Yesterday portal.azure.com wasn't reachable for a time, at least from the EU.

[lousken]

There was an outage just before crowdstrike, google MO821132

[bobbob1921]

Ouch , ok was not aware of this one. Thanks

[SoftTalker]

Crowdstrike caused a Microsoft outage. Most people don't differentiate.

[number6]

At the same time there was a Microsoft Azure outage, but it was minor compared to Croudstrike

[vel0city]

Crowdstrike caused a Crowdstrike outage for systems running Crowdstrike. The vast majority of Microsoft products and services were not affected.

[Arch485]

Except for a large part of Azure :)

[vel0city]

The failures in the Central US region in Azure were entirely unrelated to Crowdstrike. It was the day before the Crowdstrike update rolled out.

[jerrymcflurry]

No they haven't. It's Crowdstrike's bug but it's Microsoft's problem that they accepted a change in their kernel without testing.

[ryanmcbride]

Did the title change? Because it doesn't say "another outage" it says "new outage"

[skywhopper]

Is that a meaningful difference?

[ryanmcbride]

yes, do you think it's not?

[Nullabillity]

In common usage, "new outage" assumes generally assumes, well, new-as-compared-to-something-else. So yes, while the literal meanings are different, I'd interpret them as synonyms in this context.