Microsoft Has Another Outage


Let's talk about the latest hiccup in the tech world. On July 30, 2024, Microsoft 365 users around the globe were hit with a frustrating reality: services were down, and it wasn’t just a minor glitch. This was a significant outage, and it lasted nearly ten hours, leaving users struggling to access essential functions like emails, Xbox services, and other Microsoft 365 features.

So, what happened? Well, it all started at around 11:45 UTC when a Distributed Denial-of-Service (DDoS) attack targeted Microsoft’s Azure cloud services and its suite of products under Microsoft 365.

If you’re not familiar with a DDoS attack, it’s when attackers flood a network with so much traffic that it becomes overwhelmed, leading to slowdowns or complete service disruptions. In this case, the attack led to all sorts of problems—timeouts, latency spikes, and, of course, users unable to access their much-needed services.

But here’s where things took a turn for the worse. Microsoft admitted that there was an error in how their defenses were set up. Instead of mitigating the attack, the flaw in their system actually amplified the impact. That’s right—the very systems designed to protect against such attacks ended up making the situation more severe.

Microsoft didn’t just sit back and watch, though. They jumped into action, making networking configuration changes and rerouting traffic to different network paths. By 14:10 UTC, most users saw an improvement, but it wasn’t smooth sailing just yet. Some customers continued to experience issues well into the evening.

Microsoft had to roll out additional fixes across Asia Pacific, Europe, and finally, the Americas. It wasn’t until 19:43 UTC that failure rates returned to normal levels, and by 20:48 UTC, the situation was declared fully mitigated.

Now, this isn’t the first time Microsoft has dealt with such a crisis. Just two weeks before this incident, another outage rocked users due to a problematic update from CrowdStrike’s Falcon agent, causing Windows virtual machines to crash with the dreaded BSOD (Blue Screen of Death) errors. These recurring issues are raising eyebrows, especially as more businesses rely on cloud services.

The impact of this latest outage was far-reaching. Take Starbucks, for example. Their mobile ordering system went down for hours, leaving customers unable to place orders through their phones—just one example of how deeply these tech disruptions can affect everyday operations.

In response to the outage, Microsoft has promised a thorough investigation. They plan to release a Preliminary Post-Incident Review within 72 hours, followed by a more detailed Final Post-Incident Review in two weeks. These reports will shed light on what exactly went wrong and, hopefully, how they plan to prevent it from happening again.

Previous Trump Appears At NABJ Convention
Next Alina Habba Speaks At Trump Harrisburg Rally