WEB_COMPUTE builds stuck at PROVISIONING indefinitely in us-east-1 (April 13, 2026)

## Description

All WEB_COMPUTE builds for our production Amplify app in **us-east-1** are getting stuck at the **PROVISIONING** phase indefinitely with completely empty build logs. The container is never allocated, so no build commands execute.

## Details

- **App ID:** d19igjp5uug58d
- **Region:** us-east-1
- **Platform:** WEB_COMPUTE (Next.js SSR)
- **7 consecutive jobs** (214–220) all stuck at PROVISIONING since ~16:26 UTC, April 13, 2026
- **Staging app** (d2tg57oc0x7gw2) in **us-west-1** deploys the same codebase successfully in ~7 minutes (just verified)
- **No changes** to app config, IAM role, buildspec, or code between last successful deploy (Job 213, April 10) and first failure
- Even a RETRY of the last successful job (213) gets stuck at PROVISIONING
- IAM role is valid, all account quotas are healthy (3/25 apps, 1/5 concurrent jobs)

## What we've tried

1. RELEASE jobs with and without `--commit-id`
2. RETRY of last successful job (213)
3. Verified IAM role, policies, and service quotas — all healthy
4. Confirmed staging (us-west-1) deploys successfully with identical code

## Suspected cause

StatusGator reports active **CodeBuild degradation in Virginia (us-east-1)** today, with multiple user reports of "CodeBuild is not working" and "Service down" starting ~17:15 UTC. Since Amplify WEB_COMPUTE uses CodeBuild for container provisioning, this would explain the hang.

## Environment

- Build image: amplify:al2023
- Node 22, Yarn 4 (corepack)
- Framework: Next.js 16 (SSR)
- Last successful build: Job 213, April 10, 2026 (~7 min total)

No source file or test is identified. Start by comparing Amplify jobs 213–220 and the successful us-west-1 staging deployment, then verify the reported CodeBuild degradation in us-east-1; done means the provisioning failure's cause is confirmed and a recovery or owner is identified.

Written by the indexing model from the issue text.