現状 、amazonの情報しか見てないけども……
それぞれの障害情報が更新された。
数時間のうちにどうにかなるっぽいが（また誤訳か？）
誤訳だったら御免なさい。
http://status.aws.amazon.com/ より引用
Amazon Elastic Compute Cloud (N. Virginia)：仮想コンピュータ側の障害情報
10:26 AM PDT （日本時間 4/22 02:26）We have made significant progress in stabilizing the affected EBS control plane service. EC2 API calls that do not involve EBS resources in the affected Availability Zone are now seeing significantly reduced failures and latency and are continuing to recover. We have also brought additional capacity online in the affected Availability Zone and stuck EBS volumes (those that were being remirrored) are beginning to recover. We cannot yet estimate when these volumes will be completely recovered, but we will provide an estimate as soon as we have sufficient data to estimate the recovery. We have all available resources working to restore full service functionality as soon as possible. We will continue to provide updates when we have them.
11:09 AM PDT（日本時間 4/22 03:09） A number of people have asked us for an ETA on when well be fully recovered. We deeply understand why this is important and promise to share this information as soon as we have an estimate that we believe is close to accurate. Our high-level ballpark right now is that the ETA is a few hours. We can assure you that all-hands are on deck to recover as quickly as possible. Well update the community as we have more information.
Amazon Relational Database Service (N. Virginia)：データサーバー側
それぞれの障害情報が更新された。
数時間のうちにどうにかなるっぽいが（また誤訳か？）
誤訳だったら御免なさい。
http://status.aws.amazon.com/ より引用
Amazon Elastic Compute Cloud (N. Virginia)：仮想コンピュータ側の障害情報
10:26 AM PDT （日本時間 4/22 02:26）We have made significant progress in stabilizing the affected EBS control plane service. EC2 API calls that do not involve EBS resources in the affected Availability Zone are now seeing significantly reduced failures and latency and are continuing to recover. We have also brought additional capacity online in the affected Availability Zone and stuck EBS volumes (those that were being remirrored) are beginning to recover. We cannot yet estimate when these volumes will be completely recovered, but we will provide an estimate as soon as we have sufficient data to estimate the recovery. We have all available resources working to restore full service functionality as soon as possible. We will continue to provide updates when we have them.
11:09 AM PDT（日本時間 4/22 03:09） A number of people have asked us for an ETA on when well be fully recovered. We deeply understand why this is important and promise to share this information as soon as we have an estimate that we believe is close to accurate. Our high-level ballpark right now is that the ETA is a few hours. We can assure you that all-hands are on deck to recover as quickly as possible. Well update the community as we have more information.
Amazon Relational Database Service (N. Virginia)：データサーバー側
10:35 AM PDT （日本時間 4/22 02:35）We are making progress on restoring access and IO latencies for affected RDS instances. We recommend that you do not attempt to recover using Reboot or Restore database instance APIs or try to create a new user snapshot for your RDS instance – currently those requests are not being processed.
あくまでも、ブラ三の障害発生時刻や、amazonの障害発表時刻などから、
これが原因じゃないの？ という勝手な想像で記事を書いています。
この記事が誤っていたりして、他の場所に転載した場合の損害等に関しては一切責任を負いません。
またこの記事が誤っていた場合、お詫び申し上げますが、あくまでも推測記事であることをココにアナウンスいたします。
あくまでも、ブラ三の障害発生時刻や、amazonの障害発表時刻などから、
これが原因じゃないの？ という勝手な想像で記事を書いています。
この記事が誤っていたりして、他の場所に転載した場合の損害等に関しては一切責任を負いません。
またこの記事が誤っていた場合、お詫び申し上げますが、あくまでも推測記事であることをココにアナウンスいたします。