So here's what happened: on Sunday, Amazon.com, Inc.'s (AMZN) cloud division, Amazon Web Services, had a bit of a problem at one of its data centers in the United Arab Emirates. Something—objects, the company says—struck the facility, which caused sparks and then a fire. When the fire department showed up, they cut power to the site to deal with the blaze, and that included the backup generators. That's never a good sign for a data center.
The affected zone, known as mec1-az2, started having connectivity issues. If you're running things on AWS, this meant trouble for your Elastic Compute Cloud (EC2) instances, your Elastic Block Store volumes, your database services, and various networking-related APIs. In simpler terms, a chunk of the cloud in that region got a little stormy.
AWS confirmed the situation in a service update, saying, "We can confirm that a localized power issue has affected a single Availability Zone in the ME-CENTRAL-1 Region." They reported increased error rates for several EC2 networking functions, including AllocateAddress and AssociateAddress. So, if you were trying to launch new instances or manage network addresses there, you probably ran into some headaches.
The good news, if you can call it that, is that this was contained to one Availability Zone. AWS was quick to point out that other zones in the region are still humming along just fine. They recommended that customers, if they can, should use those alternate Availability Zones or even other AWS regions entirely. If you had your workloads spread across multiple zones, you likely didn't notice much. If you were all-in on the one zone that caught fire... well, that's why they tell you not to put all your eggs in one basket, or in this case, one data center.
Later on, AWS said they were "seeing significant signs of recovery" and that customers could start creating and associating new network addresses in the zones that weren't affected. However, they also noted they don't have an estimated time for when full power will be restored to the troubled zone. So, the recovery is happening, but it's not a flip-of-a-switch situation.
Now, the timing of this is... interesting, to say the least. This outage didn't happen in a vacuum. It comes as the UAE is dealing with retaliatory missile and drone strikes from Iran. Regional tensions are high. Adding another layer to the situation, President Donald Trump announced the death of Iran's Supreme Leader, Ayatollah Ali Khamenei. Trump called it "not only justice for the people of Iran, but for all great Americans" and others killed in conflicts involving Iran. It's a tense geopolitical moment, and a critical piece of internet infrastructure in the region just had a fire.
As for Amazon's stock, shares were down 0.37% in after-hours trading after closing at $210 on Friday.
