CloudFail.net

Between 9:39AM and 12:00PM PDT in the US-East-1 Region, some customers experienced problems connecting to their EC2 instances. These problems were the result of degradation in an external carrier’s link. Amazon has routed around the carrier’s degraded links until the carrier can fully resolve the issue. However, customers relying on the carrier without diverse network paths to Amazon may still be experiencing connection problems.

Between 12:33 and 12:43 AM PDT the EC2 APIs experienced increased error rates and latencies. No running instances were affected. The issue has been resolved and the service is operating normally.

We are investigating increased errors for the EC2 APIs in the US-EAST-1 Region.

Between 1:36 AM and 2:12 AM PDT the EC2 APIs experienced increased error rates and latencies. No running instances were affected. The issue has been resolved and the service is operating normally.

We are investigating increased API errors and latencies US-EAST-1 region.

We are investigating increased API errors and latencies US-EAST-1 region.

Between 4:51 PM and 11:42 PM PDT a small number of EBS volumes in the US-EAST-1 region experienced CreateSnapshot API errors. This issue has been resolved and the service is now operating normally.

A small number of volumes in the US-EAST-1 region are experiencing EBS CreateSnapshot errors. We have identified the root cause and are working on restoring functionality.

We are currently investigating EBS CreateSnapshot errors for a small number of volumes in the US-EAST-1 region.
—————————————-
[RESOLVED] EC2 API errors