Base recovers from elevated RPC and transaction-inclusion latency

What happened

Base Mainnet experienced high RPC latency, delayed transaction inclusion, and periodic inconsistencies in block-production timing before performance returned to normal.

What changed

For approximately two hours, transaction submission and state access were less reliable, degrading an operational dependency used by Base canonical-bridge workflows and monitoring.

What did not change

Base did not report a bridge exploit, asset loss, invalid state transition, changed withdrawal contract, or permanent finality-policy change.

Confirmed

• Base identified the incident at 18:58 UTC on October 20, 2025.
• The incident affected Base Mainnet public RPC and block production.
• Base reported that block building and RPC performance returned to normal at 21:07 UTC.

Still open

• Whether any canonical-bridge deposits or withdrawals were materially delayed rather than only exposed to the broader RPC and inclusion degradation.
• The root cause and any durable remediation were not stated in the retained status record.
• The retained status surface is not treated as a complete historical incident archive.

What it means for an advisor

• Review the Base bridge memo's assumptions for RPC diversity, transaction resubmission, inclusion monitoring, and block-production availability.
• Retain alternate-RPC and delayed-inclusion procedures for bridge operations; the recovered incident does not independently require restricting the bridge.