Is AWS Fargate down?
Current AWS Fargate status is UP

We continue to work towards resolving the increased networking latencies and errors affecting Availability Zones (usw2-az1 and usw2-az2) in the US-WEST-2 Region. We have now seen network mapping propagation latencies return to normal levels in both usw2-az1 and usw2-az2 Availability Zones. At this stage, all EC2 instance launches and network configuration changes are operating normally. We’re continuing to monitor network mapping latencies and will provide a final update once all has been confirmed to be operating normally.

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.

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.

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.

We can confirm increased networking latencies and errors affecting a single Availability Zone (use1-az1) in the US-EAST-1 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.