[HN Gopher] MS Azure down: An emerging issue is being investigated
       ___________________________________________________________________
        
       MS Azure down: An emerging issue is being investigated
        
       Author : williamscales
       Score  : 104 points
       Date   : 2021-04-01 21:51 UTC (1 hours ago)
        
 (HTM) web link (status2.azure.com)
 (TXT) w3m dump (status2.azure.com)
        
       | Scene_Cast2 wrote:
       | I found out about this because I almost lost a password with
       | bitwarden just now. Their "add new password" prompt is failing
       | silently.
        
       | smitop wrote:
       | Looks like this took down the national emergency alert system in
       | Canada. I'm registered as an alert LMD (last mile distributor),
       | and Pelmorex (corporation running the system just emailed me to
       | say "Please note that currently there is an unexpected
       | significant outage on Microsoft Azure that is affecting the
       | availability of the NAADS system and other clients globally. The
       | NAAD System feeds are currently not accessible. We are following
       | up on this and we will update you as soon as the issue is
       | resolved.".
       | 
       | I sure hope there aren't any emergencies in Canada until this is
       | resolved...
        
       | Nelkins wrote:
       | I don't think I get this April Fool's joke.
        
         | rvz wrote:
         | I thought this was another April Fools joke from Microsoft.
         | Then I looked at the status page and here we are.
         | 
         | Then GitHub Actions and some services stopped working and went
         | on holiday today: https://news.ycombinator.com/item?id=26666782
        
       | e0m wrote:
       | From status2.azure.com: ----------------------
       | 
       | InformationAzure DNS - Investigating
       | 
       | We are currently investigating reports of an issue affecting
       | Azure DNS. More information will be provided as it is known.
       | 
       | This message was last updated at 21:59 UTC on 01 April 2021
       | 
       | ----------------- WarningDNS issues - Investigating
       | 
       | Engineering is investigating an issue with DNS that is impacting
       | several downstream Azure services.
       | 
       | This message was last updated at 22:07 UTC on 01 April 2021
        
       | sufyanadam wrote:
       | Teams is down too
        
         | filomeno wrote:
         | It doesn't really make a difference, does it?
        
         | ceejayoz wrote:
         | I can't play Flight Simulator, even, as apparently setting up
         | offline mode requires being online.
        
           | basilgohar wrote:
           | This demonstrates one of my least favorite dark patterns of
           | recent software.
        
       | yuliyp wrote:
       | Seems like it's coming back up? Sites that were giving DNS errors
       | are now resolving for me.
        
         | mnehring wrote:
         | Yup, it does seem to be coming back alive. A 3rd party API that
         | I use is in an Azure data center. My customers were reporting
         | outages, but I just got a text from a customer that things are
         | working in real life. So, coming back up!
        
       | dustymcp wrote:
       | Just me or azure been really unstable lately atleast here in
       | europe?
        
         | bicx wrote:
         | It's not just you, and not just in Europe
        
         | semicolon_storm wrote:
         | Major worldwide outages for AAD, CosmosDB, and now DNS in just
         | the past few months so it's definitely not just you.
         | 
         | Maybe Microsoft should invest less in their shiny new AI/ML
         | platforms and more into stability of their core services.
        
       | e0m wrote:
       | We offer an API behind Azure DNS. As a hacky, but functional,
       | workaround for our customers they can manually add our server's
       | IP address to their /etc/hosts file. It'd be important for them
       | to revert that once DNS returns; however as a quick fix this
       | might help some people.
        
       | jftuga wrote:
       | All Microsoft properties are being featured on
       | https://downdetector.com/ today!
        
       | SketchySeaBeast wrote:
       | Nothing better than starting a long weekend with a client calling
       | to say their site is down and you can't even access Azure portal
       | to see what's going on.
        
       | deathanatos wrote:
       | 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, please visit our alternate Status Page
       | herehttps://status2.azure.com for more information and updates._
       | 
       | Which is the link above, and is also down for me & many others.
       | 
       | Edit: seems hit or miss. A coworker got a successful resolution
       | of status2.azure.com of 104.84.77.137 , so manually, I can get
       | there now. They're directing customers to an all green status
       | page, except for the "An emerging issue is being investigate."
       | bit at the top... (I know of at least _two_ services that are not
       | happy...)
       | 
       | It had to have been less than a month ago that AAD caused a
       | cross-service global outage. Now it's DNS. It's always DNS.
        
       | NicoJuicy wrote:
       | Everything seems to be running again.
        
       | king_magic wrote:
       | bing.com, status.azure.com, status2.azure.com - all down.
       | 
       | Can't sign into portal.azure.com, can't hit Azure File Shares,
       | etc.
       | 
       | The last outage a few days ago was enough for my company to up
       | and move most of our stuff to AWS. This new outage is enough for
       | us to fully migrate away from Azure.
       | 
       | What a cluster.
        
         | Elgolfin wrote:
         | Speaking of this. There is always this kind of conclusion every
         | time there is a major outage on a cloud provider. I am not sure
         | one is better than the others. Though, I would prefer to rely
         | on facts and numbers instead of feelings. So, is there a
         | website that monitors and keeps track of this kind of major
         | outages for all the 3 big Cloud providers (AWS, Azure, GCP)? So
         | that we can compare their resilience?
        
         | mnordhoff wrote:
         | Instead of going from relying on a single provider to relying
         | on a single provider, you could use both AWS and Azure.
        
           | reasonabl_human wrote:
           | This is the right answer from a proper dev ops and opsec POV
        
             | Elgolfin wrote:
             | The solution may have a serious cost depending on your
             | architecture. You will have to make sure it is worth the
             | investment. Replicating and keeping a whole infrastructure
             | stand-by is not an easy job for an one-hour outage.
             | Sometimes, it is not the right solution either. It really
             | depends on the business you are in.
        
         | snoshy wrote:
         | Cortana's revenge for Microsoft shutting her down.
        
           | barkingcat wrote:
           | Cortana's Revenge would be a great name for a System Shock
           | style thriller.
        
             | eurasiantiger wrote:
             | Siri Skynet Cortana sounds like a female italian mob lawyer
             | from an anime.
        
       | certifiedloud wrote:
       | Looks like L3, Azure and Google are all being affected by a DNS
       | DDoS attack.
        
         | geitir wrote:
         | how can you tell?
        
           | feyman_r wrote:
           | AWS: https://downdetector.com/status/aws-amazon-web-services/
           | 
           | Cloudflare: https://downdetector.com/status/cloudflare/
        
             | feyman_r wrote:
             | And Google too: https://downdetector.com/status/google/
        
             | ceejayoz wrote:
             | DownDetector is worthless. There's no reason to put any
             | stock in it.
             | 
             | Look at the comments on any entry and it's clear people do
             | stuff like report "outages" for Google because a random
             | website won't work in Chrome.
        
               | lima wrote:
               | The data is still useful in aggregate.
        
             | partiallypro wrote:
             | The problem with downdetector is that people say something
             | is down when really it's another service. Like with
             | Cloudflare, a lot of the comments are simply that a website
             | was down giving an CF error, but in reality it was probably
             | not CF that was down but an underlying service.
        
               | feyman_r wrote:
               | Agree on the CF part. I found it interesting that the
               | downdetector page had other cloud-providers like Google
               | and AWS showing error spikes at around the same time.
        
         | eurasiantiger wrote:
         | Just as DevOps thought of closing the lid for Easter. Nice.
        
       ___________________________________________________________________
       (page generated 2021-04-01 23:00 UTC)