Base recovers from AWS-related capacity and batch-submission disruption

What happened

An AWS outage affected Base infrastructure, reducing network capacity and interrupting batch submission on Mainnet and Testnet until service recovered.

What changed

Base Mainnet's production capacity and submission of L2 batches to Ethereum were temporarily degraded, exposing cloud-infrastructure availability as a dependency for timely canonical-bridge settlement and monitoring.

What did not change

The status record did not report a consensus failure, bridge compromise, asset loss, changed custody, or a permanent change to withdrawal or finality mechanics.

Confirmed

• Base began investigating reduced capacity at 08:23 UTC on October 20, 2025.
• Base identified a major AWS outage as affecting its infrastructure.
• Mainnet batch submission and block production were affected.
• Base reported at 09:50 UTC that batch submission resumed and transaction capacity returned to normal.

Still open

• The number and duration of affected bridge transactions were not disclosed.
• The retained record does not describe infrastructure redundancy or post-incident remediation.
• The retained status surface is not treated as a complete historical incident archive.

What it means for an advisor

• Review cloud-provider concentration and continuity assumptions in the Base canonical-bridge memo.
• Confirm that bridge operating procedures distinguish L2 inclusion from L1 batch submission and monitor both during infrastructure outages.