[ad_1]
Microsoft has experienced today a major breakdown of Azure.
The company's status page indicated that from 19:43 UTC – 05:43, in Sydney – "customers could experience intermittent connectivity problems with Azure and other Microsoft services (including M365, Dynamics, DevOps, etc.) ".
Microsoft staff "identified the underlying root cause as a DNS name resolution server delegation problem, which affects network connectivity and its downstream impact on computing, storage, and service services of application, ADA and SQL database. "
A fix was found and, at 10:10 pm UTC – 8:10 am in Sydney – Microsoft said that "mitigation measures have been applied and that engineering teams are deleting the resolver cache to mitigate." The problem is that most services are recovering. "
But the status page still reports failures and there is no indication when the full service will be restored.
The failure of DNS means that even though the Azure services are running, they can not be reached. So, the content of the comment on social media is mixed!
The good news is that all of our Azure resources (ie databases, websites, storage, containers, etc.) work perfectly!
The bad news is that we can not access it because the network infrastructure has intermittent problems. #Azure #azureoutage #outage pic.twitter.com/LG2MGh1JLQ
– əuoʎpno ןɔ ☁ (@CloudyOne) May 2, 2019
The DNS problem was resolved around 9:30 am Sydney time, but the full recovery took two extra hours.
Microsoft also provided some additional guidance on the nature of the error, writing: "To overcome this problem, the engineers have corrected the problem of naming the nameservers – the cached information has expired."
The company has promised an appropriate explanation within 72 hours.
[ad_2]
Source link