Archive for the ‘Amazon Elastic Compute Cloud (EU)’ Category.

Informational message: Increased API Errors

We are investigating elevated error rates for EBS-related API calls in the EU-WEST-1 region.

Service is operating normally: [RESOLVED] Degraded performance for some EBS Volumes

A small number of EBS volumes experienced degraded performance between approximately 7:33-7:46 PM PDT in a single Availability Zone in the EU-WEST-1 region. The system is now performing normally.

Informational message: Degraded performance for some EBS Volumes

We are investigating degraded performance for some volumes in a single Availability Zone in the EU-WEST-1 region.

Service is operating normally: [RESOLVED] Increased error rates

EBS-related API calls experienced elevated error rates from 3:26-3:58 PM PDT in the EU-WEST-1 region. The system is now functioning normally.

Informational message: Increased error rates

We are currently investigating increased EBS API error rates in the EU-WEST-1 region.

Informational message: Elastic IP ranges incorrectly blocked by some Internet anti-spam organizations.

[RESOLVED] We experienced an issue where some Elastic IP address ranges were incorrectly blacklisted by some Internet anti-spam organizations. We already handled the issue and the Elastic IP ranges were successfully whitelisted.

Service is operating normally: [RESOLVED] Elastic IP ranges incorrectly blocked by some Internet anti-spam organizations.

We experienced an issue where some Elastic IP address ranges were incorrectly blacklisted by some Internet anti-spam organizations. We already handled the issue and the Elastic IP ranges were successfully whitelisted.

Informational message: Postmortem for EU-WEST service event

We have posted a full summary and post mortem of the recent EU West service event here.

Service is operating normally: [RESOLVED] Connectivity issues

Amazon EC2 continues to operate normally in the EU-West Region. A more detailed postmortem on the cause of the recent service disruption will be forthcoming.

Informational message: [RESOLVED] Connectivity issues

Please refer to the Status History below for the prior day’s entries

Aug 11, 1:10 AM PDT The vast majority of recovery snapshots have now been created and are in customer accounts. Recovery snapshots can be identified by looking at the Description field which will contain “Recovery Snapshot vol-xxxx,” where vol-xxxx is the id of the impacted volume. If you have a snapshot or volume that is in “error” state, you should have a recovery snapshot for it and can delete the volumes and snapshots that are described as “error.” Less than 2% of the affected volumes are still in the process of having their recovery snapshot created. You can tell if your volume is part of the remaining 2% being recovered if it is in the “error” state and you do not yet see a recovery snapshot. We are continuing to work to create recovery snapshots for these remaining few volumes.
Get Adobe Flash playerPlugin by wpburn.com wordpress themes