#AWS STATUS UPDATE#

We have now restored power to the majority of instances and networking devices within the affected data center and are starting to see some early signs of recovery.

#AWS STATUS UPDATE#

Update 3: '5:18 AM PST We continue to make progress in restoring power to the affected data center within the affected Availability Zone (USE1-AZ4) in the US-EAST-1 Region. We continue to work to address the issue and restore power within the affected data center.' Connectivity and power to other data centers within the affected Availability Zone, or other Availability Zones within the US-EAST-1 Region are not affected by this issue, but we would recommend failing away from the affected Availability Zone (USE1-AZ4) if you are able to do so. We are also experiencing elevated RunInstance API error rates for launches within the affected Availability Zone.

This is affecting availability and connectivity to EC2 instances that are part of the affected data center within the affected Availability Zone. Update 2: '5:01 AM PST We can confirm a loss of power within a single data center within a single Availability Zone (USE1-AZ4) in the US-EAST-1 Region. Other Availability Zones within the US-EAST-1 Region are not affected by this issue.' Update: Amazon added the following to its status page: '4:35 AM PST We are investigating increased EC2 launched failures and networking connectivity issues for some instances in a single Availability Zone (USE1-AZ4) in the US-EAST-1 Region. AWS EC2 users report receiving messages saying: 'An error occurred fetching instance data: An unknown error occurred.' The AWS Status Page does not currently show any current errors, but says that there was an issue with the Elastic Beanstalk console in multiple Regions earlier today that has since been resolved.

Aws status