Microsoft’s report says Azure fac a DDoS attack, which affect the performance of its cloud worldwide for about six hours.
Microsoft announc that its Azure cloud was hit by a distribut denial of service cyberattack on Tuesday, July 30, which caus disruptions to some of its services.
You may be interest in reading: Microsoft services on the canvas
According to the company’s reporting site , “between 11:45 (UTC standard time) – 17:45 Central Mexico time – it detect the attack.
Which at 19:43 UTC on July 30, 2024 – 01:43 on July 31 in Mexico – approximately manag to mitigate.
“The affect services were:
Azure App Services, Application Insights, Azure IoT Central, Azure Log Search Alerts, Azure Policy, as well as the Azure portal itself and some Microsoft 365 and Microsoft Purview tools.”
What caus the failure?
The company describes that it fac an canada whatsapp number data unexpect increase in usage that caus the issue in the Azure Front Door and Azure Content Delivery Network components .
As a result, they perform below acceptable service thresholds, resulting in intermittent errors, timeouts, and latency spikes.
These increases, the text describes, were generat by a distribut denial of service (DDoS) attack , which activat its protection mechanisms.
But it said its initial investigations suggest that an error in the implementation of its defenses amplifi the impact of the attack rather than mitigating it.
The attack was resolv almost eight hours later
“Once we understood the nature of the usage spike, we implement network configuration changes to support our DDoS protection efforts and sharing a framework that will enable you to keep perform failovers to alternate network paths to provide relief,” the document states.
Services are restor
Initial network cmo email list configuration changes successfully mitigat most of the impact by 14:10 UTC (20:10 Mexico time).
However, some customers report availability below 100%, which they began to mitigate around 18:00 UTC (00:00 in Mexico).
The report states that failure rates return to pre-incident levels at 19:43 UTC (01:43 on July 31 in Mexico) .