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

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.

We continue to work on resolving the error rates and increased delays in network propagation for newly launched EC2 instances in a single Availability Zone (use-az2) in US-EAST-1 Region. We have seen some improvement in mapping propagation times in the majority of the affected cells within the Availability Zone (use-az2) but continue to work on fully understanding the root cause of the event. We continue to recommend shifting network traffic away from the affected Availability Zone (use-az2) if you are able to do so.

We can confirm increased networking latencies and errors affecting multiple Availability Zones (usw2-az1 and usw2-az2) in the US-WEST-2 Region. We have identified a potential root cause of the errors and are attempting mitigations. Early signs are this mitigation is reducing error rates and latencies. We continue to work towards a full root case and recovery.

We are working to accelerate the rate at which Lambda asynchronous invocations are processed, and now estimate that the queue will be fully processed over the next hour. We expect that all queued invocations will be executed.

Lambda synchronous invocation APIs have recovered. We are still working on processing the backlog of asynchronous Lambda invocations that accumulated during the event, including invocations from other AWS services (such as SQS and EventBridge). Lambda is working to process these messages during the next few hours and during this time, we expect to see continued delays in the execution of asynchronous invocations.