Is AWS NAT Gateway down?
Current AWS NAT Gateway status is UP

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 continue to progress toward resolving the increased networking latencies and errors affecting Availability Zones (usw2-az1 and usw2-az2) in the US-WEST-2 Region. At this time, we are approximately 50% completed with the update to address resource contention within the subsystem responsible for network mappings propagation in the usw2-az2 Availability Zone. Once we complete the update in usw2-az2, we will then move on to usw2-az1. Our current expectation is to have both Availability Zones fully resolved within the next 60 to 90 minutes, and we will continue to provide updates as recovery progresses.

We continue to make progress towards resolving the increased networking latencies and errors affecting a single Availability Zone (use1-az1) in the US-EAST-1 Region. The issue affects some instances in this Availability Zone, where network mappings are not being propagated to the underlying hardware. Any mutations (or changes) to the networking configurations - including launching an EC2 instance, attaching and Elastic IP address or Elastic Network Interface - would see delayed propagation times, which will affect network connectivity until completed. Other networking services like PrivateLink and API Gateway, are also seeing network connectivity issues where network mappings have been mutated. For other AWS services, such as Lambda and Container Services (ECS/EKS), delays in function and container creation, as well as increased error rates, may occur due to this issue.

We continue to see improvements in the use1-az1 Availability Zone. We recommend that customers avoid making mutating changes within the affected Availability Zones, which will ensure that no new network mappings need to be propagated to the underlying hardware, avoiding impact from this issue.

We will continue to keep you updated as we make progress towards full recovery.

We continue to investigate increased networking latencies and errors affecting Availability Zones (usw2-az1 and usw2-az2) in the US-WEST-2 Region. The issue affects some instances in each of these Availability Zones, where network mappings are not being propagated to the underlying hardware. Any mutations to network configurations would see delayed mappings, which will affect network connectivity. Other networking services like PrivateLink and API Gateway, are also seeing network connectivity issues where network mappings have been mutated. For other AWS services, such as Lambda and Container Services (ECS/EKS), delays in function and container creation, as well as increased error rates, may occur due to this issue.

We have been working to resolve the issue and are seeing improvements in the usw2-az1 Availability Zone as a result of these efforts. We will continue to keep you updated as we make progress towards full recovery.