# Base recovers from mainnet transaction delays caused by missed blocks

> Timely mainnet transaction inclusion was temporarily impaired, creating operational delay risk for bridge initiation, proof, and other Base transactions even though no bridge-specific transaction was identified.

- URL: https://riadefi.com/on-chain/2026-05-14-coinbase-bridge-missed-blocks-transaction-delays/
- Type: Market stress
- Stage: Recovery reported
- Evidence: confirmed
- Materiality: material
- Event date: 2026-05-14
- Version: 1, published 2026-08-22 (first published 2026-08-22)
- Advisor-relevant: yes
- Affects: Base canonical bridge (protocol)

## What happened

Base experienced an elevated rate of missed mainnet blocks. Transactions submitted during missed blocks were delayed until a later successful block, and Base marked the incident resolved the following day.

## What changed

Timely mainnet transaction inclusion was temporarily impaired, creating operational delay risk for bridge initiation, proof, and other Base transactions even though no bridge-specific transaction was identified.

## What did not change

The notice did not report a complete chain halt, transaction reorganization, fund loss, canonical-bridge exploit, or change to withdrawal and upgrade controls.

## Confirmed

- Base began investigating elevated missed blocks on May 13, 2026 at 16:44 UTC.
- Transactions submitted during missed blocks were delayed until the next successful block.
- The incident affected Base mainnet block production.
- Base marked the incident resolved on May 14, 2026 at 05:04 UTC.

## Still open

- The cause of the elevated missed-block rate and remediation applied.
- The total number and maximum delay of affected transactions.
- Whether any deposit, withdrawal, proof, or finalization transactions experienced materially longer processing.
- The recurrence risk under comparable block-production conditions.

## What it means for an advisor

- Review Base bridge assumptions for sequencer and block-production availability.
- Maintain transaction-status checks and resubmission procedures for bridge operations during elevated missed-block periods.
- The recovered event does not establish current unavailability but should remain in the Base operational incident record.

## Sources

1. [Delayed Transactions](https://status.base.org/incidents/0h468wjw300f) · Base Status · 2026-05-13


---

Published by Ketju Research on RIADeFi (https://riadefi.com). Educational research for financial professionals; not investment, legal, tax, or compliance advice.