.webp)
Extended Downtime Affects Cloud Services Amid Configuration Change Issues
Microsoft Azure has recently resolved a significant outage that disrupted services for customers across North and Latin America. The incident, which began around 18:22 UTC, lasted more than two hours and impacted multiple services dependent on Azure Front Door (AFD), the company’s cloud Content Delivery Network (CDN).
Microsoft initially attributed the outage to a “configuration change” that led to widespread service interruptions. “This issue is impacting multiple geographies, mostly in North America and Latin America,” the company stated on its Azure status page. The problem was promptly addressed when Microsoft rolled back the configuration change at 19:25 UTC, leading to a recovery for most services. Many Microsoft services automatically switched away from AFD in response to the issue.
Despite these efforts, customers also reported issues connecting to Azure services, including Azure DevOps, in the United Kingdom and Brazil. Additionally, the Azure status page, which failed to update for over an hour, was inaccessible for many users during the outage. Downdetector logged thousands of reports related to server connection and login problems, although the Service Health Status page initially showed no issues.
This outage follows a recent major disruption affecting Microsoft 365 and Azure services last Tuesday, which was attributed to an “unexpected usage spike.” Microsoft later identified issues with AFD and CDN components, leading to intermittent errors and performance problems.
Microsoft has been working to ensure stability and reliability for its customers, striving to prevent future disruptions and maintain service excellence.
.webp)
