Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft Azure Outage

twitter.com

Post reply on HN
Print view View original

131–140 of 247 posts

Re: Microsoft Azure Outage

#131

Post by wrldos »

jiggawatts wrote: post #118
wrldos wrote: post #59

Earlier quoted context omitted.

Migrating stuff off it now to AWS (not my stuff). Couldn't agree more. Total shit show.

Curious to hear about the specifics...

Persistent problems between Azure VMs and virtual disks causing unexpected reboots. Complete outages. And don't even start me on ACI (for Windows). It doesn't even work.

In 7 years we had one AWS AZ outage and we didn't even notice because our monitoring platform in there couldn't reach the network (learned something!). But nothing broke. Even the us-east-1 outages didn't affect us.

Re: Microsoft Azure Outage

#132

Post by hnarn »

steve1977 wrote: post #83
nosebear wrote: post #40

I'm hearing from four different friends from four different companies in Germany that they can't really work right now.

If they were relying on Outlook and Teams to be productive, they probably couldn't really work before either.

What a naive comment. As if the only truly important jobs exist in engineering and require nothing but git and a book on C.

Re: Microsoft Azure Outage

#134

Post by magicalhippo »

throwaheyy wrote: post #101
gerdesj wrote: post #94

Earlier quoted context omitted.

It involves a lot of private browsing sessions which is actually MS's recommendation! What a PITA.

Nah I just set up a 2nd browser profile, and they both stay signed in. It’s a breeze.

Or Firefox containers?

Re: Microsoft Azure Outage

#135

Post by Jochim »

dustedcodes wrote: post #18

Azure is the most developer hostile cloud environment. I have zero sympathy for people being affected by this because if you voluntarily use Azure then this is what you deserve. Sorry for being so miserable, but Azure has given me soooo much grief over the last 10 years that I'm just completely done with this shitshow of a platform.

I quite like Microsoft/Azure from a development perspective. If you're running .NET, Application Insights alone is nearly enough to put it above the competition. I appreciate how it integrates with AZD/Teams and the platform as a whole felt much more cohesive than AWS.

The monthly $60-$100 developer credit was fantastic as well. It avoided the usual fighting for approval/budget to test things out.

Re: Microsoft Azure Outage

#136

Post by hdjjhhvvhga »

UK-AL wrote: post #103
saghm wrote: post #64

Earlier quoted context omitted.

Someone has to "approve" the status pages showing what's actually happening? From a customer perspective, it seems far worse to have status pages fail to reflect actual outages than to have them accidentally report an outage when there isn't one because no one really cares about what the status page says if they're not having issues. It's hard to see how the goal here could be anything other than trying to add plausi…

You can't approve a fact.

As others noted, the so-called "status" pages of big service providers don't serve to reflect reality but to shape it. For actual status you need to consult independent monitoring services.

Re: Microsoft Azure Outage

#137

Post by wrldos »

maushu wrote: post #41
NKosmatos wrote: post #11

What's the point of having a status page if it doesn't indicate the issues? https://status.azure.com/en-us/status Azure, Teams, Outlook are almost down from Greece and Germany, and their status page shows that everything is fine :-)

The point is PR. Never trust a status page if it's not directly connected to the monitoring system.

They never attach it to the monitoring because monitoring systems usually generate a lot of false positives which affect their published SLA.

Re: Microsoft Azure Outage

#138

Post by InsomniacL »

tialaramex wrote: post #102
ngrilly wrote: post #53

Earlier quoted context omitted.

Nothing is forcing companies to sign an Azure contract with Microsoft, and go with AWS or GCP instead. Perhaps they are just doing something right. But I didn't use Azure myself. I'd be curious to know what's good or bad about it compared to GCP and AWS.

For a development team, here's an example of something good about Azure: Microsoft gives us dev accounts with monthly Azure credits (e.g. $100) and you cannot spend more when those credits run out because there is no credit card etc. behind that account to charge the excess. Azure just like other cloud services (I've used AWS but as I understand it GCP is the same) doesn't believe in timely billing. You can and will…

> I work for a University, I suspect that if you paid full price for these services it makes no economic sense, a $100 Azure credit that cost $100 is a bad deal

For Cloud to make economic sense, you need to treat it very differently from traditional infrastructure. For example, simply shutting down our Dev environment outside of business hours saves means we're not paying for the compute the majority of the time.

Re: Microsoft Azure Outage

#139

Post by mattclarkdotnet »

vineyardmike wrote: post #111
saghm wrote: post #64

Earlier quoted context omitted.

Someone has to "approve" the status pages showing what's actually happening? From a customer perspective, it seems far worse to have status pages fail to reflect actual outages than to have them accidentally report an outage when there isn't one because no one really cares about what the status page says if they're not having issues. It's hard to see how the goal here could be anything other than trying to add plausi…

> it seems far worse to have status pages fail to reflect actual outages than to have them accidentally report an outage when there isn't one Thats not the goal. > It's hard to see how the goal here could be anything other than trying to add plausible deniability for what would otherwise be obvious deception Thats the goal. The "status page" is considered the source of truth for most of the big contracts. If status-p…

Utter rubbish. Major contracts have account managers and it all gets hashed out 1-1.

Re: Microsoft Azure Outage

#140

Post by polack »

wrldos wrote: post #137
maushu wrote: post #41

Earlier quoted context omitted.

The point is PR. Never trust a status page if it's not directly connected to the monitoring system.

They never attach it to the monitoring because monitoring systems usually generate a lot of false positives which affect their published SLA.

Then they should have a "?" status that can be triggered by automated systems that acknowledge that it looks to be an issue but that they are manually investigating.

If it's a false positive they just resolve it without it affecting SLA and if it's a real problem then us customers wouldn't have to debug our own stack for 2 hours before Microsoft informs us that they are the problem.

EDIT: Wonder how many man-years of extra debugging work their non-working status page have caused the customers.

Post reply on HN