Ouch, and login.microsoftonline.com too - i.e. SSO using MS accounts. We'd just rolled that out across most (all?) of our internal systems... And microsoft.com too - that's gotta hurt
I am still stunned people choose to do this, considering major Office 365 outages are basically a weekly thing now.
Tell HN: Azure outage
151–160 of 841 posts
Re: Tell HN: Azure outage
#152FYI: https://status.cloud.microsoft/
Re: Tell HN: Azure outage
#153Re: Tell HN: Azure outage
#1542026: the year of your own metal in a rack
Re: Tell HN: Azure outage
#155downdetector reports coincident cloudflare outage. is microsoft using cloudflare for management plane, or is there common infra? data center problem somewhere, maybe fiber backbone? BGP?
Re: Tell HN: Azure outage
#156Re: Tell HN: Azure outage
#157I'm mid-deployment, but thankfully it seems to be running ok so far. Just the portal is not working so my visibility is not good.
Re: Tell HN: Azure outage
#158Earlier quoted context omitted.
Mind-boggling that any retailer would not have the capability to at least run the checkout stations offline.
I knew an old guy in the '00s who specialized in cobal/fortran for working on tiller software. Guess he retired and they couldn't maintain it
Re: Tell HN: Azure outage
#159Earlier quoted context omitted.
I'll be interested in the incident writeup since DNS is mentioned. It will be interesting in a way if it is similar to what happened at AWS.
It's pretty unlikely. AWS published a public 'RCA' https://aws.amazon.com/message/101925/ . A race condition in a DNS 'record allocator' causing all DNS records for DDB to be wiped out. I'm simplifying a bit, but I don't think it's likely that Azure has a similar race condition wiping out DNS records on _one_ system than then propagates to all others. The similarity might just end at "it was DNS".
Re: Tell HN: Azure outage
#160Currently standing in a half closed supermarket because the tills are down and they cant take payments