Base recovers from missed-block transaction delays

What happened

Base experienced a high rate of missed blocks. Transactions submitted during missed blocks were delayed until a subsequent successful block, after which the condition resolved without a reported intervention.

What changed

The incident added a confirmed transaction-inclusion disruption to Base's operating history, followed by recovery and preparation of a mitigation for recurrence.

What did not change

The status record does not report a canonical-bridge contract exploit, fund loss, withdrawal pause, state reorganization, or permanent change to bridge mechanics.

Confirmed

• Base reported a high rate of missed blocks.
• Transactions sent during missed blocks were delayed until the next successful block.
• Base reported that the issue resolved itself.
• Base said it prepared a mitigation for use if the issue returned.

Still open

• The status record does not state the root cause or incident duration.
• It does not quantify missed blocks, delayed transactions, or affected users.
• It does not establish whether any canonical-bridge deposits, proofs, or withdrawal finalizations were delayed.

What it means for an advisor

• Record the event in the Base canonical bridge's chain-liveness history.
• Monitor recurrence because bridge use depends on Base transaction inclusion even when bridge contracts remain intact.
• No approval restriction is supported by this isolated, recovered incident, but repeated missed-block events would warrant review.