none
Azure down - Until when? RRS feed

  • Question

  • There are currently serious issues with Windows Azure. The dashboard shows it's being worked on. Since we rely heavily on Windows Azure, we've been monitoring the dashboard closely the entire day.

    What I've noticed is a complete lack of estimates on  issues will be resolved. For instance, take a look at http://www.microsoft.com/windowsazure/support/status/RSSFeed.aspx?RSSFeedCode=WACNE. For the last 4 hours, the status has essentially been "The restoration steps to mitigate the issue are underway.".

    What is the reasons behind Microsoft not informing its customers when the issue will be resolved?

    Is there not even a guess how long time it may take?


    Nitramafve

    Wednesday, February 29, 2012 7:29 PM

Answers

  • Hi Ranjit,

    In Azure Service Dashboard, i find Windows Azure Compute [North Central US] status is Performance degradation. So maybe there is still something wroing with Azure Compute on North Central US, here is details:

    29-Feb-12
    10:55 AM UTC We are experiencing an issue with Windows Azure Compute in the North Central US sub-region. Incoming traffic may not go through for a subset of hosted services in this sub-region. Deployed applications will continue to run. There is no impact to storage accounts either. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    12:30 PM UTC We are still troubleshooting this issue and capturing all the data that will allow us to resolve it. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    1:45 PM UTC We are executing restoration steps to mitigate the issue. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    2:30 PM UTC We have determined that about 6.7% of hosted services in this sub-region are impacted by this issue. The restoration steps to mitigate the issue are underway. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    3:30 PM UTC The restoration steps to mitigate the issue are underway. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    4:30 PM UTC The restoration steps to mitigate the issue are still underway. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    5:30 PM UTC The restoration steps to mitigate the issue are still underway. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    6:30 PM UTC The restoration steps to mitigate the issue are still underway. This incident impacts Access Control 2.0, Marketplace, Service Bus and the Access Control & Caching Portal in the same regions where Windows Azure Compute is impacted. As a result affected customers may experience a loss of application functionality. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    7:30 PM UTC We are actively recovering Windows Azure hosted services in this sub-region. More and more customers applications should be back up-and-running even if service management functionality is not yet restored. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    8:30 PM UTC We have recovered over half of the Windows Azure hosted services that were impacted. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    9:30 PM UTC Recovery efforts are still underway. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    10:30 PM UTC Recovery efforts are still underway. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    11:30 PM UTC Recovery efforts are still underway, we are 70% through the recovery process and we restored full service management functionality for more customers in this region. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    1-Mar-12
    1:00 AM UTC Recovery efforts are still underway. The majority of Windows Azure customers and services have been restored. However, a few customers and services remain affected and we are working aggressively to restore full functionality. We restored full service management functionality for most customers in this region. We have published a recap of the incident since it started on the Windows Azure team blog (http://blogs.msdn.com/b/windowsazure/archive/2012/03/01/windows-azure-service-disruption-update.aspx). Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    3:00 AM UTC We are working on stabilizing the Windows Azure Platform as well as following-up with all customers who were impacted by this incident. The recovery process continues. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    4:30 AM UTC Recovery efforts are still underway, we are 85% through the recovery process in terms of impacted hosted services. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    7:30 AM UTC Our recovery efforts to restore compute service to impacted customers in this sub-region are complete. A small number of customers in this sub-region may face long delays during service management operations. We request any customers experiencing compute or service management issues in this sub-region to reach out to us through the support channel described on this site: (http://www.windowsazure.com/en-us/support/contact). We apologize for any inconvenience this incident causes our customers.

    Hope it can help you.


    Please mark the replies as answers if they help or unmark if not. If you have any feedback about my replies, please contact msdnmg@microsoft.com Microsoft One Code Framework

    Thursday, March 1, 2012 10:05 AM
    Moderator

All replies

  • Hi,

    As far as i know, most of Azure services is available now, check their status form Azure Service Dashboard:

    http://www.windowsazure.com/en-us/support/service-dashboard/

    For the incident for the Azure Portal, see RSS feed:

    http://www.microsoft.com/windowsazure/support/status/RSSFeed.aspx?RSSFeedCode=WAPortalWW

    Hope it can help you.


    Please mark the replies as answers if they help or unmark if not. If you have any feedback about my replies, please contact msdnmg@microsoft.com Microsoft One Code Framework

    Thursday, March 1, 2012 7:44 AM
    Moderator
  • We were facing lot of issues yesterday. But today we are able to create new deployments but still not able to delete old deployments on services on North Central US.

    So everything getting back to track. but unfortunate it happened in the first place.


    - Ranjit (If you found this post useful, Please "Mark as Answer" or "Vote as Helpful)

    Thursday, March 1, 2012 9:46 AM
  • Hi Ranjit,

    In Azure Service Dashboard, i find Windows Azure Compute [North Central US] status is Performance degradation. So maybe there is still something wroing with Azure Compute on North Central US, here is details:

    29-Feb-12
    10:55 AM UTC We are experiencing an issue with Windows Azure Compute in the North Central US sub-region. Incoming traffic may not go through for a subset of hosted services in this sub-region. Deployed applications will continue to run. There is no impact to storage accounts either. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    12:30 PM UTC We are still troubleshooting this issue and capturing all the data that will allow us to resolve it. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    1:45 PM UTC We are executing restoration steps to mitigate the issue. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    2:30 PM UTC We have determined that about 6.7% of hosted services in this sub-region are impacted by this issue. The restoration steps to mitigate the issue are underway. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    3:30 PM UTC The restoration steps to mitigate the issue are underway. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    4:30 PM UTC The restoration steps to mitigate the issue are still underway. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    5:30 PM UTC The restoration steps to mitigate the issue are still underway. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    6:30 PM UTC The restoration steps to mitigate the issue are still underway. This incident impacts Access Control 2.0, Marketplace, Service Bus and the Access Control & Caching Portal in the same regions where Windows Azure Compute is impacted. As a result affected customers may experience a loss of application functionality. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    7:30 PM UTC We are actively recovering Windows Azure hosted services in this sub-region. More and more customers applications should be back up-and-running even if service management functionality is not yet restored. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    8:30 PM UTC We have recovered over half of the Windows Azure hosted services that were impacted. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    9:30 PM UTC Recovery efforts are still underway. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    10:30 PM UTC Recovery efforts are still underway. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    11:30 PM UTC Recovery efforts are still underway, we are 70% through the recovery process and we restored full service management functionality for more customers in this region. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    1-Mar-12
    1:00 AM UTC Recovery efforts are still underway. The majority of Windows Azure customers and services have been restored. However, a few customers and services remain affected and we are working aggressively to restore full functionality. We restored full service management functionality for most customers in this region. We have published a recap of the incident since it started on the Windows Azure team blog (http://blogs.msdn.com/b/windowsazure/archive/2012/03/01/windows-azure-service-disruption-update.aspx). Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    3:00 AM UTC We are working on stabilizing the Windows Azure Platform as well as following-up with all customers who were impacted by this incident. The recovery process continues. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    4:30 AM UTC Recovery efforts are still underway, we are 85% through the recovery process in terms of impacted hosted services. Further updates will be published to keep you apprised of the situation. We apologize for any inconvenience this causes our customers.
    7:30 AM UTC Our recovery efforts to restore compute service to impacted customers in this sub-region are complete. A small number of customers in this sub-region may face long delays during service management operations. We request any customers experiencing compute or service management issues in this sub-region to reach out to us through the support channel described on this site: (http://www.windowsazure.com/en-us/support/contact). We apologize for any inconvenience this incident causes our customers.

    Hope it can help you.


    Please mark the replies as answers if they help or unmark if not. If you have any feedback about my replies, please contact msdnmg@microsoft.com Microsoft One Code Framework

    Thursday, March 1, 2012 10:05 AM
    Moderator