Update: Amazon EC2 Problems On-Going, Resolution Delayed

As an update to our earlier post, we report continued issues coming out of East Region of Amazon Web Service’s (AWS) EC2 service. Until they restore access to the instances and volumes located in the affected Zone, we will continue to have degraded or limited service available to our end users.

The AWS team continues to update their own Health Status Page, though information is sparse and remains vague. Though they originally provided an estimate of “a few hours” in the 11:09 PT update, they have re-iterated the same predicted time to resolution in the 18:18 PT update.

To ensure the integrity of all data and all accounts, we are waiting patiently and eagerly for the AWS team to complete their recovery tasks and bring service back.

Again, we apologize for the inconvenience and delay. We will keep you updated throughout the next several hours.

2 thoughts on “Update: Amazon EC2 Problems On-Going, Resolution Delayed

  1. Rufus Mangrove

    As a user of elephantdrive, it is one thing to announce (and deflect responsibility in my mind) that because of AMAZON AWS, there’s a severe problem with the network. . .

    The most obvious question, the 1000000 pound gorilla, is this: CAN YOU DETERMINE BEYOND ANY DOUBT THE INTEGRITY OF THE ITEMS THAT HAVE BEEN SAVED IN THE “CLOUD.”? In my mind, this is the fundamental question that we want to know NOW. Thanks.

    • Hi Rufus,

      Thanks for your patience and a for a great question. The storage of user objects is handled by the S3 service and there have be no alerts or failures of any kind associated with S3 during this outage, so that underlying data is not in jeopardy. That said, until we get full access back (which appears to be finally in progress – see next post for more), we are basing our reports on information we still need to verify.

      Also, we are sharing responsibility with Amazon for the duration of this outage. Firstly, we chose them as a vendor after careful consideration, so any issues arising from their efforts that affect users result from ElephantDrive’s choice. Secondly, having seen this incident play out, we could have made different architectural decisions that would have reduced (though not eliminated) downtime.

      More to come as soon as we have the information…

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s