Amazon EC2 Server Issues Cause Web Havoc

Amazon’s Elastic Compute Cloud (EC2) service has caused a bit of disarray around the web as servers have failed. Among the sites/services affected are Foursquare, Quora, Reddit, and Hootsuite (h...
Amazon EC2 Server Issues Cause Web Havoc
Written by Chris Crum

Amazon’s Elastic Compute Cloud (EC2) service has caused a bit of disarray around the web as servers have failed.

Among the sites/services affected are Foursquare, Quora, Reddit, and Hootsuite (ht: The Next Web).

The issues appear to be coming out of Virginia. Amazon is providing updates on its Amazon Webservices Service Health Dashboard. All of the issues come from that location. One sequence of udpates attached to Amazon Cloudwatch reads:

2:26 AM PDT We are working on restoring connectivity to a small number of EC2, EBS, and RDS resources in multiple availability zones in the US-EAST-1 region. While we restore connectivity, CloudWatch metrics for those resources will be delayed.

3:04 AM PDT We are continuing to see connectivity issues impacting EC2, EBS, and RDS resources in multiple availability zones in the US-EAST-1 region. While we restore connectivity, CloudWatch metrics for those resources will be delayed. We continue to work towards resolution.

4:47 AM PDT CloudWatch metrics are delayed for some EBS and RDS resources in the US-EAST-1 region. The delays began at 12:55AM PDT. We have isolated the impact to a single availability zone, and are working towards a full resolution.

Another on Amazon Relational Database Service says:

1:48 AM PDT We are currently investigating connectivity and latency issues with RDS database instances in the US-EAST-1 region.

2:16 AM PDT We can confirm connectivity issues impacting RDS database instances across multiple availability zones in the US-EAST-1 region.

3:05 AM PDT We are continuing to see connectivity issues impacting some RDS database instances in multiple availability zones in the US-EAST-1 region. Some Multi AZ failovers are taking longer than expected. We continue to work towards resolution.

4:03 AM PDT We are making progress on failovers for Multi AZ instances and restore access to them. This event is also impacting RDS instance creation times in a single Availability Zone. We continue to work towards the resolution.

5:06 AM PDT IO latency issues have recovered in one of the two impacted Availability Zones in US-EAST-1. We continue to make progress on restoring access and resolving IO latency issues for remaining affected RDS database instances.

On AWS CloudFormation, it says:

3:29 AM PDT We are experiencing delays in creating and deleting stacks that include EBS, EC2 and RDS resources in multiple availability zones in the US-EAST-1 region. Existing stacks are not impacted.

5:10 AM PDT CloudFormation stack creation and deletion is delayed for stacks containing EC2, EBS and RDS resources in the US-EAST-1 region. The delays began at 12:55AM PDT. We have isolated the impact to a single availability zone, and are working towards a resolution.

Finally, on AWS Elastic Beanstalk, it says:

3:16 AM PDT We can confirm increased error rates impacting Elastic Beanstalk APIs and console, and we continue to work towards resolution.

4:18 AM PDT We continue to see increased error rates impacting Elastic Beanstalk APIs and console, and we are working towards resolution.

The rest of the list comes with the “service is operating normally” status.

Foursquare and Reddit seem to be back on track, but Quora and Hootsuite are still down at the time of this writing.

I wonder how much money is being lost based on Amazon’s server issues.

Get the WebProNews newsletter delivered to your inbox

Get the free daily newsletter read by decision makers

Subscribe
Advertise with Us

Ready to get started?

Get our media kit

Advertise with Us