# Base transaction-delay resolution

> Base deployed a fix on October 30 at 19:28 UTC and subsequently reported that the delays had ended.

- URL: https://riadefi.com/on-chain/2026-10-30-base-mainnet-inclusion-delays/
- Type: Market stress
- Stage: Recovery reported
- Evidence: confirmed
- Materiality: material
- Event date: 2026-10-31
- Version: 2, published 2026-11-01 (first published 2026-10-31)
- Follow-up: 2026-11-02
- Advisor-relevant: yes
- Affects: Base canonical bridge (protocol)

## What happened

Base reported resolution of transaction inclusion delays on October 31 at 16:37 UTC.

## What changed

Base deployed a fix on October 30 at 19:28 UTC and subsequently reported that the delays had ended.

## What did not change

Base reported normal block production during the incident. Its notice does not establish any change to bridge withdrawal terms.

## Confirmed

- Base began investigating slower transaction inclusion on October 29 at 16:34 UTC.
- Base reported that some transactions could take longer to receive inclusion or preconfirmation.
- Base marked the incident resolved on October 31.

## Still open

- Base did not quantify the longest transaction delay or identify affected bridge withdrawals.
- Base did not explain the root cause in this notice.

## What it means for an advisor

- Ketju should check whether delayed bridge transactions exceeded the timing assumptions in the Base memo.
- The notice does not establish censorship beyond the documented force-inclusion window.

## Sources

1. [Delayed transaction inclusion on Base Mainnet](https://status.base.org/incidents/7xj799fyhrlx) · Base · 2026-10-29


---

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