This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(108.80000000000001, 10%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDS%3C/text%3E%3C/svg%3E)
Our app services have been experiencing lots of downtime since yesterday afternoon.
We can see in the Azure Portal health advisories that there is apparently a big issue in the Canada East region (where almost all of our app services are).
Why is this not reported on https://status.dev.azure.com/ ? That shows Canada East as being all green checks.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 80%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGP%3C/text%3E%3C/svg%3E)
Samr thing here. Problem does show on only one of our ressource group in Canada east.... But takes forever to be resolved.
Hi,
https://status.dev.azure.com/ will show status pertaining to Azure DevOps and its components only and not the actual Azure services
For Azure services like App Service please check Azure Status: https://status.azure.com/en-us/status
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 55.00000000000001%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
DanielStout-5066 and GuyProvost-1052 - Firstly, we regret the inconvenience this issue has caused.
As PratikSomaiya mentioned, https://status.dev.azure.com/ dashboard shows service health pertaining to Azure DevOps.
--Copying the notification posted from one of my affected subscriptions on Azure Portal @Azure Service Health.
“
Summary of Impact: Starting at 18:52 UTC on 03 Mar 2022, you have been identified as a customer who may have experienced availability or service management issues with their resources hosted in Canada East region of Azure.
Preliminary Root Cause: We determined a configuration dependency between Gen7 and Gen8 hardware to have affected the Gen7 hardware that was marked for decommissioning.
Mitigation: Reinstalling the correct Gen7 hardware drivers helped to recover the host nodes. However, some of the failures encountered during the recovery process resulted in an increase of mitigation time. Post correcting the failures, self-healing process took place to recover the impacted services and hence fully mitigating the issue.
Next Steps: We apologize for the impact to affected customers. for the We will continue to investigate to establish the full root cause and prevent future occurrences.
Stay informed about Azure service issues by creating custom service health alerts: https://aka.ms/ash-videos for video tutorials and https://aka.ms/ash-alerts for how-to documentation.
“
Additional info:
Azure Service Health provides personalized alerts and guidance when Azure service issues affect you. It can notify you, help you understand the impact of issues, and keep you updated as the issue resolves.
Azure Resource Health helps you diagnose and get support for service problems that affect your Azure resources. It reports on the current and past health of your resources.
Azure status page is a global view of the health of all Azure services in all regions. Reports on service problems that affect a broad set of Azure customers.
--Once again, apologies for the inconvenience with this issue,. Kindly be assured that we have relayed this feedback to our product engineering team. Thank for your cooperation!
---
To benefit the community find the right answers, please do mark the post which was helpful by clicking on ‘Accept Answer’ & ‘Up-Vote’.
Oops, I pasted the wrong link.
The status was not reported on this status page: https://status.azure.com/en-ca/status
I know I can see the status updates in the portal, but where is the public display of this issue?
If you look at the history at https://status.azure.com/en-us/status/history/ there is no indication of any issue. Considering this was basically a complete 1.5 day outage for all our app services it certainly seems like this should have been reported on the status page!
No worries about the wrong URL, Daniel. Thanks for the follow-up.
Since the outage did not affect the broader set of Azure customers, so it wasn't reported on the Azure Status page. It had only affected a few minor subset of customers and those affected subscription received the personalized notification on Azure Service Health.
I completely understand the situation and the inconvenience it could have caused; we apologize for this trouble. I have relayed this internally to our teams.