Base recovers from congestion-related transaction-inclusion delays

What happened

Periodic congestion on Base Mainnet delayed transaction inclusion from October 17 into October 18. Base increased mempool size and reported the incident resolved.

What changed

Transactions could remain pending longer during congestion, and Base changed mempool capacity to improve inclusion speed. This temporarily degraded execution reliability for canonical-bridge-related transactions.

What did not change

The official record did not report a bridge exploit, asset loss, failed finality, or a change to bridge custody or withdrawal contracts.

Confirmed

• Base began reporting periodic congestion and delayed transaction inclusion at 19:27 UTC on October 17, 2025.
• The incident affected the Base Mainnet transaction pool.
• Base increased mempool size and marked the incident resolved at 03:34 UTC on October 18.

Still open

• Whether the mempool increase fully addressed recurrence under comparable congestion.
• Whether any bridge transaction exceeded an applicable client timing tolerance.
• The retained status surface is not treated as a complete historical incident archive.

What it means for an advisor

• Review transaction-expiry, resubmission, and pending-state monitoring procedures for Base bridge activity.
• Record congestion and mempool capacity as operational dependencies without treating the resolved event as a permanent bridge restriction.