Is AWS CodeBuild down?
Current AWS CodeBuild status is UP

We continue to investigate increased error rates and latencies for the DynamoDB APIs in the US-WEST-2 Region. We have seen 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 usw2-az2. At this stage, all EC2 instance launches and network configuration changes in usw2-az2 are operating normally. We have seen strong recovery in usw2-az1 as well and will provide an update when network propagation latencies have returned to normal levels there as well.

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. While we continue to make progress in addressing the issue, we wanted to provide some more details on the issue. Within Amazon Virtual Private Cloud (VPC) any changes to the network configuration - including launching an EC2 instance, attaching an Elastic IP address or Elastic Network Interface - needs to be propagated to the underlying hardware to ensure that network packets can flow between source and destination. We call this network configuration “network mappings”, as it contains information about network paths or mappings. Starting at 10:00 AM PDT this morning, we have been experiencing a delay in the propagation of these mappings within a single cell (part of the Availability Zone) in usw2-az1 and usw2-az2 Availability Zones. The root cause appears to be increased load to the subsystem responsible for the handling of these network mappings. We have been working to reduce the load on this service to improve propagation times, but while we have made some progress, mapping propagation latencies have not returned to normal levels. We continue to work to identify all forms of resource contention that could be leading to load, and have a few additional updates that we are currently working on.

Once we have reduced the load on the subsystem responsible for network mapping propagation, we would expect full recovery. Since the issue only affects networking mappings as a result of changes to the network configuration, avoiding any mutating changes to your network configuration in the affected Availability Zone would limit impact.

For customers looking to fail away from the affected Availability Zone or Region, please ensure that you are not relying on mutating network configuration in the affected Availability Zones as part of that process.

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

We can confirm increased Build error rates in the US-EAST-1 Region. We have identified the root cause and are working toward resolution.

6:26 AM PDT We are investigating an issue where customers may run into errors preventing them from creating new builds in the US-EAST-1 Region.