Microsoft Confirms the Latest Outage Caused by Cyber-Attack: Here’s How the Internet Reacted

Microsoft's 365 services experienced another global outage on Tuesday, July 30, affecting users worldwide. This marks the second major disruption within a month, following a significant outage less than two weeks ago that impacted various sectors, including travel and market operations.

The company revealed that preliminary investigations indicate the latest outage was triggered by a cyber-attack. Between approximately 11:45 UTC and 19:43 UTC on July 30, 2024, some customers faced issues connecting to several Microsoft services globally.

Affected services included Azure App Services, Application Insights, Azure IoT Central, Azure Log Search Alerts, Azure Policy, the Azure portal itself, and parts of Microsoft 365 and Microsoft Purview services.

Microsoft stated that the initial trigger was a Distributed Denial-of-Service (DDoS) attack. This attack activated their DDoS protection mechanisms. However, initial investigations suggest an error in implementing these defenses amplified the attack's impact instead of mitigating it.

"While the initial trigger event was a Distributed Denial-of-Service (DDoS) attack, which activated our DDoS protection mechanisms, initial investigations suggest that an error in the implementation of our defenses amplified the impact of the attack rather than mitigating it," said Microsoft.

This incident highlights ongoing challenges in cybersecurity for major tech companies. The repeated outages underscore vulnerabilities even in well-established systems like Microsoft's.

As users worldwide faced disruptions again, questions arise about the robustness of current cybersecurity measures. The recent events have put pressure on Microsoft to enhance its defense mechanisms against such attacks.

The company is expected to conduct a thorough investigation to prevent future occurrences. Ensuring robust security protocols will be crucial for maintaining user trust and service reliability.

The company further said the team will be completing an internal retrospective to understand the incident in more detail. They are said to share a Preliminary Post Incident Review (PIR) within approximately 72 hours, to provide more details on what happened and how they responded. After the internal retrospective is completed, the company will also share the Final Post Incident Review with any additional details and learnings.

Here are some of the most trending posts related to Microsoft's latest outage that we spotted on X, previously Twitter.