Amazon Web Services experienced an outage in its US-East-1 region that knocked hundreds of online services offline on Friday, March 2. The outage, resulting from two separate 10-minute power outages affecting AWS’ network peering facility, affected customers over a period of two hours.
Companies affected by the outage include Atlassian, which operates popular productivity services like Trello, Bitbucket, and Jira. Twilo, which provides support services for companies like Netflix, Zendesk, and Lyft was also impacted.
We are seeing a recovery with our cloud provider, AWS, and Atlassian products and services are recovering with it. We will continue to monitor and post updates on our Statuspage: https://t.co/pR95HIdc3m
— Atlassian (@Atlassian) March 2, 2018
Slack, a popular communications solution for companies and individuals, reported connection problems between 6:41 and 7:21 AM PST on Friday.
Dozens of other services including GitHub, MongoDB, and Zillow reported outages during that time period.
For many users, the impact of the outage came to their Alexa devices, which lost its voice during the incident only to have it return by mid-afternoon.
DownDetector.com, which tracks connection issues and outage reports across social media, indicated that Alexa was down between 9:39 AM EST and 2:30 PM EST.
On Monday, March 5, an AWS spokesman told CNBC in an email that the issues arose after a power loss at “one of AWS’s redundant internet connection points in Virginia,” which affected “a small number of AWS customers” using Direct Connect in the US-East-1 region.
Similarities to Another Big East Coast Outage One Year Ago
The timing of this outage coincides with the one-year anniversary of another disruption that impacted the same Northern Virginia (US-East-1) region on February 28th, 2017. In this case, an incorrect command used by an S3 team member resulted in the unexpected removal of a large number of S3 servers.
The result was an interruption of services for the region that lasted between 9:37 AM and 1:54 PM PST on that day. A similar time frame to the one Amazon experienced last Friday.
This latest interruption was brief, and for many customers, redundant services existed in other regions which picked up the slack. Amazon said that for many companies, the issue was limited to some increased latency and occasional packet loss.
As of this article’s writing, all AWS services in North America are operating normally. You can check AWS service status at any time using Amazon’s Service Health Dashboard.