AWS status (made simple)

Current status - Oct 22, 2020 PDT

North America

All services are operating normally

South America

All services are operating normally

Europe

All services are operating normally

Asia Pacific

All services are operating normally

Service interruptions for the past week

North America

All services were operating normally

South America

All services were operating normally

Europe

All services were operating normally

Asia Pacific

Amazon Elastic Compute Cloud (Tokyo) Oct 21, 2020 PDT [RESOLVED] ネットワーク接続性の問題 | Network Connectivity Issues

8:10 PM PDT AP-NORTHEAST-1リージョンのアベイラビリティゾーン(APNE1-AZ2)における一部のEC2インスタンスおよびEBSボリュームのパフォーマンス低下に関するネットワーク接続性の問題を調査しております。 | We are investigating network connectivity issues for some EC2 instances and degraded volume performance for some EBS volumes in a single Available Zone (APNE1-AZ2) in the AP-NORTHEAST-1 Region.
8:41 PM PDT 一部のEC2インスタンスに影響を与えていたネットワーク接続性の問題は解消しました。AP-NORTHEAST-1リージョンのアベイラビリティゾーン(APNE1-AZ2)における一部のEBSボリュームのパフォーマンス低下の問題については、引き続き調査を行っております | The networking connectivity issues affecting some EC2 instances have been resolved but we continue to investigate degraded performance for some EBS volumes within the affected Availability Zone (APNE1-AZ2) in the AP-NORTHEAST-1 Region.
9:15 PM PDT 日本時間11:42から11:53の間、AP-NORTHEAST-1リージョンのアベイラビリティゾーン(APNE1-AZ2)における一部のインスタンスにおいて、ネットワーク接続性の問題がありました。また、日本時間11:42から13:09の間、同アベイラビリティゾーンにおける一部のEBSボリュームにおいて、ボリュームパフォーマンスの低下がありました。問題は解消し、現在正常に稼働しております | Between 7:42 PM PDT and 7:53 PM PDT we experienced network connectivity issues for some instances in a single Availability Zone (APNE1-AZ2) in the AP-NORTHEAST-1 Region. Between 7:42 PM and 9:09 PM PDT, we also had degraded volume performance for some EBS volumes in that Availability Zone. The issue has been resolved and the service is operating normally.

Amazon Elastic Compute Cloud (Sydney) Oct 21, 2020 PDT EC2 Instance Meta Data Service Errors

7:28 PM PDT We are investigating increased errors for the EC2 Instance Meta Data Service in the AP-SOUTHEAST-2 Region. Applications within the instance attempting to query the Instance Meta Data Service may experience increased errors or timeouts. Since the Instance Meta Data Service may be used during the operating system boot process, some instances may be experiencing launch failures. We are working to resolve the issue.
8:46 PM PDT We continue to investigate increased errors for the EC2 Instance Meta Data Service in the AP-SOUTHEAST-2 Region. We are seeing the most impact for newly launched instances. Applications within the instance attempting to query the Instance Meta Data Service may experience increased errors or timeouts. We are working to resolve the issue.
9:58 PM PDT We have identified the root cause and resolved the issue causing increased errors and timeouts for the EC2 Instance Meta Data Service for newly launched instances in the AP-SOUTHEAST-2 Region. From 9:26 PM PDT, newly launched instances are no longer experiencing increased errors and timeouts for the EC2 Instance Meta Data Service. Instances that were affected by this issue will self-recover over the coming hours, but for immediate recovery, we recommend relaunching, or stopping and starting, the affected instances to resolve the issue. The issue has been resolved and the service is operating normally.

Why this site? Because it's frustrating scrolling the infinite AWS status page looking for any issue in the AWS infrastructure. This site only shows the issues, anything else it's just ok.

Warning: This site is not maintained by or affiliated with Amazon in any way. Information is scraped from AWS status site and the data shown is not guaranteed to be accurate or current. Last Update: 10/22/2020 05:10 PDT