Is AWS Glue down?
Current AWS Glue 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 make progress towards resolving the increased networking latencies and errors affecting Availability Zones (usw2-az1 and usw2-az2) in the US-WEST-2 Region. In the last 30 minutes, we’ve applied an update to address resource contention within the subsystem responsible for network mappings propagation and are seeing early signs of improvement. We will continue to monitor before deploying this change more broadly and will continue to provide updates.

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 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 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.