# Base's resolved transaction inclusion delays

> Base attributed delayed and dropped pending transactions to unexpected mempool congestion.

- URL: https://riadefi.com/on-chain/2026-10-24-base-transaction-inclusion-delays/
- Type: Market stress
- Stage: Recovery reported
- Evidence: confirmed
- Materiality: material
- Event date: 2026-10-24
- Version: 1, published 2026-10-28 (first published 2026-10-28)
- Follow-up: 2026-10-29
- Advisor-relevant: yes
- Affects: Base canonical bridge (protocol)

## What happened

Base reported resolved transaction inclusion delays on October 24, according to its official status notice.

## What changed

Base attributed delayed and dropped pending transactions to unexpected mempool congestion.

## What did not change

Base's notice establishes no change to bridge contracts, withdrawal rules, or custody authority.

## Confirmed

- Base marked the incident resolved at 12:30 UTC on October 24, 2026.
- Base attributed the incident to unexpected mempool congestion.

## Still open

- Base did not state the incident's start time or number of affected transactions.
- Base did not identify affected bridge transactions or quantify holder losses.

## What it means for an advisor

- Ketju should check whether the incident changes the memo's assumptions about submitting bridge transactions during congestion.
- Advisors should confirm transaction inclusion before treating a holder's bridge request as submitted.

## Sources

1. [Base transaction inclusion delays](https://status.base.org/incidents/9v8w1pcww9rx) · Base · 2026-10-24


---

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