CloudFail.net

Between 5:15 AM and 7:16 AM PST a single availability zone in the US-EAST-1 Region experienced delays in VPC Elastic IP associations. The issue has been resolved and the service is operating normally.

We are currently investigating delays in the associations of VPC Elastic IPs in a single availability zone in the US-EAST-1 Region.

From 11:05 PST to 11:55 PST the Sao Paulo (GRU1) edge location experienced elevated error rates affecting some object requests. The Service is now operating normally.

Between 2:55AM PST and 4:15AM PST DNS resolution for requests to Amazon S3 buckets in the US-Standard region addressed using bucketname.s3.amazonaws.com failed. Requests addressed using s3.amazonaws.com/bucketname succeeded. The issue has been corrected and DNS resolution is operating normally.

We are currently investigating increased error rates for S3.

DNS resolution is impacted for bucket names with virtual hosts (i.e., .s3.amazonaws.com) in the US Standard region. Requests for buckets with virtual names that have already been resolved are being served.

Between 11:09 AM and 12:04 PM PST EBS APIs experienced elevated latencies in the US-EAST-1 region and there were also elevated launch failures for EBS backed instances. For a portion of that time, a small number of existing EBS volumes briefly experienced increased IO latencies. The service is now operating normally.

We are investigating increased latencies for the EBS APIs and elevated launch failures for EBS backed instances in the US-EAST-1 Region.

Between 2:57 AM and 3:20 AM PST, ElasticMapReduce API requests were failing in the US-WEST-1 region. The issue has been corrected and the service is operating normally.

Requests to S3 in the EU-WEST-1 region between 10:37AM PST to 10:41AM PST and 11:18AM PST to 11:22AM PST experienced higher than normal error rates. The issue is now resolved and the service is operating normally.