Latest Posts

Stay in Touch With Us

[vc_empty_space height=”9px”]

For Advert Placement;

Email

info@plat4om.com

Follow us on social Media

  /  Tech   /  Daily-Briefs   /  Microsoft Explains Why It Had An Outage Last Week
Microsoft

Microsoft Explains Why It Had An Outage Last Week

On April 1, 2021, Microsoft experienced a massive outage across most of its services, which were rooted in DNS issues with Azure. Now, the company has released a more detailed status update explaining what caused Azure to fail to respond to queries (via ZDNet).

 

According to the update on the Azure status history page, there was an unusual surge in Azure DNS queries from all over the world, which Azure’s systems are designed to mitigate through “layers of caches and traffic shaping”. However, a specific series of events exposed an error in the code for Azure’s DNS service, which made it less efficient.

 

Things only got worse as clients faced errors because subsequent DNS retries only resulted in more traffic piling up. Microsoft has systems in place that would usually drop illegitimate DNS queries that cause volumetric spikes like this; but because many of the queries were retries, they were considered legitimate. As such, the DNS services became unavailable after some time.

Also Read:
– Microsoft Bags Yet Another HoloLens Contract With US Military
– Microsoft Is Reportedly In Talks To Acquire Discord For $10 Billion
– Facebook, Uber And Microsoft Will Soon Be Going Back To Their Offices

Microsoft says the issues started at 9:21PM UTC and by 10:00PM, Azure services themselves had been fixed; with additional capacity also being prepared if further mitigation was needed. However, this time exceeded Microsoft’s goal for fixing problems like this. Many Microsoft services depend on Azure and recovery times were different for each of them; but by 10:30PM, most services were back online.

 

Following the outage, Microsoft says it updated the logic on its mitigation systems to prevent excessive retries; and it will continue working to improve the detection and mitigation of volumetric spikes in traffic. Naturally, the DNS code defect was also fixed; so hopefully, accidents like this won’t happen anytime soon.

 

 

For your daily dose of tech, lifestyle, and trending content, make sure to follow Plat4om on Twitter @Plat4omLive, on Instagram @Plat4om, on LinkedIn at Plat4om, and on Facebook at Plat4om. You can also email us at info@plat4om.com and join our channel on Telegram at Plat4om. Finally, don’t forget to subscribe to our YouTube channel HERE.

Post a Comment

Solve : *
30 ⁄ 10 =