Displaying mobile view Desktop view
|Web & Mobile|
|Data & Storage|
|SQL Database Management Portal|
|SQL Data Sync|
|SQL Data Warehouse|
|Media & CDN|
|Live and On-Demand Streaming|
|Identity & Access Management|
|Azure Active Directory|
|Azure Active Directory B2C|
|Access Control Service|
|Visual Studio Online|
|Visual Studio Application Insights|
|Azure Management portal|
|Azure Resource Manager|
|Microsoft Azure preview portal|
SUMMARY OF IMPACT: Between 13:55 and 18:00 on 8 Oct 2015 UTC some Service Bus customers deployed in West Europe experienced intermittent connectivity failures to their Service Bus Queues and Topics. PRELIMINARY ROOT CAUSE: Preliminary investigation shows that one of the supporting backend SQL databases was in a degraded state. MITIGATION & NEXT STEPS: Engineers have identified and corrected a degraded database issue, and validated that normal functionality has returned to the service. We will now investigate the underlying root cause of this issue and develop a solution to prevent reoccurrences.
Starting on 8 Oct, 2015 from approx. 05:15 to 16:05 UTC, some Service Bus customers deployed in West Europe may have experienced intermittent connectivity failures to their Service Bus queues. Engineers have identified and corrected a database issue that likely caused the interruption to service however this is still pending a full investigation. We now expect normal functionality to have returned to the service.
At 07 Oct, 2015 04:23 UTC our Engineers received monitoring alerts for SQL Database in the East US sub-region. We have concluded our investigation of the alerts and confirmed that all services are healthy, and a service incident did not occur.
Starting at 06 Oct, 2015, 03:25 to 7:05 UTC, a subset of customers using Visual Studio Online \ Build in East US 2 may have experienced high build queue times and build completions may have taken longer than expected. Engineers have now restored normal functionality to the service. Further details may also be available at http://aka.ms/vsoblog
We have confirmed that the Visual Studio Online \ Build issue Starting at 06 Oct, 2015 03:25 UTC was limited to East US2, and did NOT have any impact for customers in East US. Investigation into impact for East US 2 customers will continue separately.
SUMMARY OF IMPACT: From 06 Oct, 2015 03:50 to 05:12 UTC a subset of customers using Virtual Machines and Storage in North Europe may have experienced issues accessing their services located in this region. Some customers may have experienced a Virtual Machine reboot. PRELIMINARY ROOT CAUSE: This interruption was triggered by a platform bug in Storage deployment infrastructure which caused a component required for the VM disk partition to become temporarily unavailable. MITIGATION & NEXT STEPS: Azure engineering team mitigated the issue by restoring Storage avaialbility, and is implementing a protection mechanism to prevent this from happening again.
From 5 Oct, 2015 8:42 UTC to 17:59 UTC customers using SQL Database in West Europe, South Central US and East US may have experienced issues accessing services. New connections to databases in this subscription in these regions may have resulted in an error or timeout. Existing connections remained available to accept new requests, however if those connections were terminated then re-establishing them may have failed. This incident has now been mitigated.
From 5 Oct, 2015 13:48 UTC to 19:19 UTC customers using Visual Studio Online \ Build in North Central US may have experienced high build queue times and build completions could have taken longer than expected. See the VSO blof for more details: http://aka.ms/VSOblog - This incident is now mitigated.
From 17:59 to 21:04 UTC on 2 Oct, 2015 a subset of customers using Web Apps deployed in North Europe may have experienced timeouts or 500 errors while attempting to connect to their Web App services. Engineers have deployed a mitigation. This incident has now been mitigated.
From 16:31 to 18:39 UTC on 2 Oct, 2015 a subset of customers using Web Apps deployed in West Europe may have experienced timeouts or 500 errors while attempting to connect to their Web App services. Engineers have deployed a mitigation. This incident has now been mitigated.