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

MS Azure down: An emerging issue is being investigated

status2.azure.com

Post reply on HN
Print view View original

101–110 of 131 posts

Re: MS Azure down: An emerging issue is being investigated

#101

Post by easton »

medium_burrito wrote: post #84
thetinguy wrote: post #76

Earlier quoted context omitted.

The major cloud providers all aim for 99.999% uptime. Keep in mind that 99.99% uptime means ~4 minutes of downtime a month. I think there are other reasons that banks may not want or have the ability to run their core services on the cloud.

Let's be honest, it's Azure. The only reason you choose it is because either you compete with Amazon in some way, or you hate your infrastructure engineers, or don't know better.

Or because you already use Microsoft mail, so you already have Azure AD there, and they sent you some credits in an email, and then...

I think Azure is cheaper for certain workloads as well, and at one point had DCs in places where AWS didn't. But it's mostly the "we already buy X Microsoft product, and they cost about the same, so..."

Re: MS Azure down: An emerging issue is being investigated

#102

Post by joenathanone »

certifiedloud wrote: post #4

Looks like L3, Azure and Google are all being affected by a DNS DDoS attack.

From my support ticket

>As discussed, we found that your case could be part of a global scale incident wherein multiple Dynamics services were rendered inaccessible due to a suspected Azure DDoS attack. This issue started at approximately 21:30 UTC on 1st April 2021 and, along the symptoms, our customers may experience intermittent issues accessing Microsoft services, including Azure, Dynamics, and Power Automate. On this regard, the Microsoft teams involved have rerouted traffic to separate resilient DNS services and are seeing improvement in service availability. With this confirmation, as agreed, I will proceed to lower the severity of this case and transfer it for an agent working in your time zone to continue following up with you and confirm these services have returned to an expected operational state.

Re: MS Azure down: An emerging issue is being investigated

#103

Post by abarringer »

bartread wrote: post #92
deathanatos wrote: post #2

Edit: it seems like it might be over. So, the outage appears to be that DNS for `azure.com` and maybe also `windows.net` (blob storage for us, but I'm not sure) is not resolving. So, the OP's link here is broken. Tweets indicate that it might be intermittently resolving. https://twitter.com/AzureSupport/status/1377737333307437059 > Warning sign We are aware of an issue affecting the Azure Portal and Azure services, p…

It was less than a month ago and, with us starting our migration to Azure which is due to complete by mid-June, I'm getting decidedly jumpy about the amount of downtime. Our current provider, with whom we have a number of dedicated servers, might be piss poor in some ways (takes ages to get changes made, lack of pricing transparency, kind of expensive for what they are), but I don't remember the last time they had an…

What I truly don't get is everyone compares piss poor on-prem servers with premium cloud offerings.

Sure, you can screw up on prem. But if you are only marginally competent spinning up services/servers/clusters takes but an instant, it's dirt cheap, and vastly more reliable.

Our only significant outages in the past 10 years have been our services dependent on big clouds. Including the Pre-Thanksgiving AWS one last year.

AWS outage history here https://en.wikipedia.org/wiki/Timeline_of_Amazon_Web_Service...

Re: MS Azure down: An emerging issue is being investigated

#106

Post by nonbirithm »

ceejayoz wrote: post #40
lima wrote: post #36

Earlier quoted context omitted.

The data is still useful in aggregate.

Marginally, if anything. Non-technical users misattribute and misunderstand causes of outages. There’s a comment on the AWS page complaining that iTunes gift cards are being slow to arrive. The Google page has people who think the comments are the place to talk to Google support. A major outage will make itself known in far clearer ways.

My broadband provider was down (Wave G) and had no status page. Social media was silent. The only way I could confirm it was an outage and not my local network setup was by using downdetector.

I wish those companies would actually have status pages.

Re: MS Azure down: An emerging issue is being investigated

#107

Post by nonbirithm »

deathanatos wrote: post #2

Edit: it seems like it might be over. So, the outage appears to be that DNS for `azure.com` and maybe also `windows.net` (blob storage for us, but I'm not sure) is not resolving. So, the OP's link here is broken. Tweets indicate that it might be intermittently resolving. https://twitter.com/AzureSupport/status/1377737333307437059 > Warning sign We are aware of an issue affecting the Azure Portal and Azure services, p…

This is not even the first time that Azure has had single-point-of-failure DNS issues.

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

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

Re: MS Azure down: An emerging issue is being investigated

#108

Post by paulryanrogers »

abarringer wrote: post #103
bartread wrote: post #92

Earlier quoted context omitted.

It was less than a month ago and, with us starting our migration to Azure which is due to complete by mid-June, I'm getting decidedly jumpy about the amount of downtime. Our current provider, with whom we have a number of dedicated servers, might be piss poor in some ways (takes ages to get changes made, lack of pricing transparency, kind of expensive for what they are), but I don't remember the last time they had an…

What I truly don't get is everyone compares piss poor on-prem servers with premium cloud offerings. Sure, you can screw up on prem. But if you are only marginally competent spinning up services/servers/clusters takes but an instant, it's dirt cheap, and vastly more reliable. Our only significant outages in the past 10 years have been our services dependent on big clouds. Including the Pre-Thanksgiving AWS one last ye…

> Sure, you can screw up on prem. But if you are only marginally competent spinning up services/servers/clusters takes but an instant, it's dirt cheap, and vastly more reliable.

Do you mean on premise you can spin up virtual servers and virtual clusters instantly? Because I imagine you'd have to order, physically rack, and setup the bare metal if one doesn't have the capacity already.

Re: MS Azure down: An emerging issue is being investigated

#109

Post by iJohnDoe »

paulryanrogers wrote: post #108
abarringer wrote: post #103

Earlier quoted context omitted.

What I truly don't get is everyone compares piss poor on-prem servers with premium cloud offerings. Sure, you can screw up on prem. But if you are only marginally competent spinning up services/servers/clusters takes but an instant, it's dirt cheap, and vastly more reliable. Our only significant outages in the past 10 years have been our services dependent on big clouds. Including the Pre-Thanksgiving AWS one last ye…

> Sure, you can screw up on prem. But if you are only marginally competent spinning up services/servers/clusters takes but an instant, it's dirt cheap, and vastly more reliable. Do you mean on premise you can spin up virtual servers and virtual clusters instantly? Because I imagine you'd have to order, physically rack, and setup the bare metal if one doesn't have the capacity already.

Exactly. Sure, my cousin Earl can spin up a container and some VMs. Will they be secure? Probably not. Will they be backed up and offsite failover? Probably not. Will they get ransomware at some point? Probably.

There is no need to make blanket statements about on-prem vs. cloud. You have to weigh the pros and cons as any other business decision.

It’s about controlling you’re own destiny with either decision.

Re: MS Azure down: An emerging issue is being investigated

#110

Post by russellendicott »

paulryanrogers wrote: post #108
abarringer wrote: post #103

Earlier quoted context omitted.

What I truly don't get is everyone compares piss poor on-prem servers with premium cloud offerings. Sure, you can screw up on prem. But if you are only marginally competent spinning up services/servers/clusters takes but an instant, it's dirt cheap, and vastly more reliable. Our only significant outages in the past 10 years have been our services dependent on big clouds. Including the Pre-Thanksgiving AWS one last ye…

> Sure, you can screw up on prem. But if you are only marginally competent spinning up services/servers/clusters takes but an instant, it's dirt cheap, and vastly more reliable. Do you mean on premise you can spin up virtual servers and virtual clusters instantly? Because I imagine you'd have to order, physically rack, and setup the bare metal if one doesn't have the capacity already.

Yeah. I used to work for a mid sized company and they did a lot of on-prem. Even there it took a lot of lead time to add 20 physical nodes to a cluster.

Now I work for an Global Enterprise and the benefits of cloud aren't necessarily about reliability--they're more about the speed and efficiency that pet projects can be spun up and spun down without international labor laws and multi-year leases.

Post reply on HN