Is AWS Glue down?
Current AWS Glue 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 continue to experience elevated API error rates in a single Availability Zone (usgw1-az1) in the US-GOV-WEST-1 Region. We are working on multiple parallel paths to mitigate the issue. Instances currently running remain 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. While we do not have an estimate for recovery at this time, we are tracking the progress and will provide you with another update by 11:45 AM PDT.

We continue to investigate increased error rates and latencies for the DynamoDB APIs in the US-WEST-2 Region. We have seem some improvement in error rates over the last 15 minutes but customers may still be experiencing errors. We continue to work on resolving the issue and will keep you updated on our progress.

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.