Microsoft Azure suffers outage after cooling issue

by pcunite on 9/4/2018, 5:28 PM with 108 comments
  • by amaccuish on 9/4/2018, 9:57 PM

    The Azure status page has more information. I suggest updating the link.

    > A severe weather event, including lightning strikes, occurred near one of the South Central US datacenters. This resulted in a power voltage increase that impacted cooling systems. Automated datacenter procedures to ensure data and hardware integrity went into effect and critical hardware entered a structured power down process.

    https://azure.microsoft.com/en-us/status/

  • by Someone1234 on 9/4/2018, 9:58 PM

    Visual Studio Online has been offline all day. They say it is due to the same Azure outage. This has had a productivity impact.

    If Microsoft didn't own GitHub, this may have prompted a move, but since they do it seems a little redundant given that Github will likely be on Azure too before long.

    https://blogs.msdn.microsoft.com/vsoservice/?p=17405

  • by king_magic on 9/4/2018, 10:31 PM

    Edit: <snipped> out my rant.

    It's been a long day because of this. Just going to leave it at that.

  • by dmarlow on 9/5/2018, 12:38 AM

    The worst part has been the poor communication. If they were to give clearer insight from the get go, that'd give me more confidence and patience. Saying "check back in 2 hours" isn't useful.

  • by GFischer on 9/4/2018, 8:14 PM

    We're affected by this issue. And we had our alerts system in Azure as well, so we didn't get alerts about the outage (welp).

  • by addicted on 9/5/2018, 2:38 AM

    VSTS is still down for us. TFS hosted code repos along with our entire bug system on VSTS means that no work is being done.

    I suspect we are gonna have to wait at least one other day at best for this to resolve. Meanwhile my local code goes even more out of sync.

    I’m probably just gonna spin up a git repo on my local machine and use that to share code with my team.

  • by ledriveby on 9/5/2018, 2:06 AM

    Kind of surprised of the lack of redundancy, especially for their first party products. Shouldn't they be deploying to more than one failure zone?

  • by Memosyne on 9/4/2018, 10:16 PM

    The Visual Studio Marketplace is also down https://marketplace.visualstudio.com/.

  • by plasma on 9/5/2018, 12:27 AM

    The outage appears to be ongoing, and its having ripple affects in other regions (management portal unresponsive, autoscale and other services not firing in West US at least for me).

    Also unable to lodge a support ticket because the portal fails to identify me as having paid support (that API request appears to timeout).

  • by gameswithgo on 9/5/2018, 12:35 AM

    Yeah our company's website was down all day due to this. We are looking at ways to mitigate in the future.

  • by pcunite on 9/5/2018, 12:47 AM
  • by karmicthreat on 9/4/2018, 9:48 PM

    So AWS has had some big outages, as has Azure. Has GCP had any big outages yet?

  • by filomeno on 9/5/2018, 8:29 AM

    We all ditched the Unix model of a central server with dumb terminals around because Microsoft told us the future was everybody having a full OS in their workstation. Now they tell us the future is going back 30 years, and having all of our data and programs in somebody else's machines (theirs).

    Sometimes I can't understand people.

  • by partiallypro on 9/4/2018, 10:22 PM

    You can use a VPN to view the status page if it's erroring out for you, I'd also suggest trying to clear your local DNS cache.

  • by p2t2p on 9/4/2018, 9:59 PM

    And I was wondering why my App.Gateways are not deploying last night

  • by tracker1 on 9/5/2018, 12:04 AM

    The Extensions Marketplace for VS Code also seems offline, still.

  • by vdchuyen on 9/7/2018, 6:29 AM

    I suggest major cloud providers should exchange their critical services hosting on each other, at least status page or some critical authentication/authorization API functions.