CloudFail.net

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.

Eventual consistency convergence times and 404 No Such Key responses are within normal ranges. The service is operating normally.

Eventual consistency convergence times remain normal for incoming PUT requests. Our current estimate for convergence for the complete subset of objects that were uploaded earlier and have not yet converged is 11 PM PST, but we expect convergence for the vast majority of keys to complete in the next hour or so.

Eventual consistency convergence times remain normal for incoming PUT requests. We are continuing to work on convergence for a subset of objects that were uploaded earlier. We are making incremental progress on convergence, but our current estimate is that consistency may not be achieved for all affected objects until 11PM PST this evening. We are continuing to actively work on accelerating this.

Eventual consistency convergence times have now returned to normal for incoming PUT requests. We are now working on accelerating convergence for the subset of objects that were previously PUT and have not yet converged. Though these objects may not yet be accessible, if you received a 200 “OK” response then the object was successfully stored.

Our current estimate is that consistency may not be achieved for all affected objects until tomorrow, though we are actively working to accelerate this and we are making incremental progress. If you have objects that have not yet become consistent and you need others to be able to access them more quickly, you may want to consider re-uploading those objects as eventual consistency convergence is now happening in a normal timeframe for new PUT requests.

Eventual consistency convergence times have now returned to normal for incoming PUT requests. We are now working on accelerating convergence for the subset of objects that were previously PUT and have not yet converged. Though these objects may not yet be accessible, if you received a 200 “OK” response then the object was successfully stored.

Our current estimate is that consistency may not be achieved for all affected objects until tomorrow, though we are actively working to accelerate this and we are making incremental progress. If you have objects that have not yet become consistent and you need others to be able to access them more quickly, you may want to consider re-uploading those objects as eventual consistency convergence is now happening in a normal timeframe for new PUT requests.

We are continuing to experience longer than normal eventual consistency delays in the US-Standard region. You may receive a 404 error “No Such Key” when trying to GET an object that you recently PUT and/or recently PUT objects may not be included in LIST results. We are working to resolve the issue, but continue to expect longer than normal eventually consistency convergence times for a subset of PUTs.

We are continuing to experience longer than normal eventual consistency delays in the US-Standard region. You may receive a 404 error “No Such Key” when trying to GET an object that you recently PUT and/or recently PUT objects may not be included in LIST results. We are working to resolve the issue, but continue to expect longer than normal eventually consistency convergence times for a subset of PUTs.