Is Amazon Elastic Kubernetes Service down?
Current Amazon Elastic Kubernetes Service status is UP

We are seeing broad signs of recovery for the increased API error rates and failures for new instance launches in a single Availability Zone (usgw1-az1) in the US-GOV-WEST-1 Region. Customers may still see some API error rates while our mitigation efforts complete, however, retries would likely succeed. We will provide you with another update by 1:30 PM PDT.

We are experiencing elevated API error rates in a single Availability Zone (usgw1-az1) in the US-GOV-WEST-1 Region. Instances currently running are unaffected, however, API calls to create, modify or terminate the instances in the affected Availability Zone are not working. APIs calls directed to launch instances targeting the non-impacted Availability Zones are working. We have identified the root cause and are working to mitigate the issue.

We have identified the root cause for the increased delays in EC2 instance and Status Check metrics, including DescribeInstances and DescribeInstanceStatus API results, in a single Availability Zone (use2-az1) in the US-EAST-2 Region. During this time, some alarms on delayed metrics may transition into an INSUFFICIENT_DATA state. Launching and terminating instances are not affected, but the status of these actions may be delayed. We will provide another update by 2:30 PM PDT.

We are investigating increased API error rates for the EC2 APIs in the US-EAST-1 Region. This is mainly affecting the DescribeInstanceTypes, DescribeInstanceTypeOfferings and DescribeReservedInstancesOfferings APIs. During this time, customers may receive an Internal Error displayed in the Management Console under the "Instance Types" section. We are actively working on identifying the root cause. We will provide another update by 2:30 PM PDT, or sooner if we have additional information to share.

We can confirm that customers are experiencing elevated error rates for cluster upgrade operations in the US-EAST-1 Region. This is a result of actions we took to mitigate additional customer impact following the EC2 network propagation event yesterday in a single Availability Zone (use1-az2). For EKS customers, we have purposely disabled cluster upgrade operations to prevent any impact to existing clusters and running applications. We have identified the root cause for the underlying issue and are working towards mitigating the current impact. We will enable cluster upgrade operations once the issue is resolved. We will provide an update within the next 60 minutes, or sooner if we have additional information to share.