Coinbase’s Base network disclosed that a stale journal state bug in its sequencer block-building logic caused two separate block production outages on June 25 and June 26, 2026, halting transactions on one of Ethereum’s largest layer-2 networks.
What Base said about the two outages
Base’s official postmortem confirmed that the first outage on June 25 lasted 116 minutes, with block sequencing resuming at 17:51 UTC after investigators traced the halt to block 47806542. For related coverage, see Ark Invest Adds Coinbase, Circle, Bullish, Robinhood.
The second incident struck the following day, June 26. This time, the outage lasted 20 minutes before service was restored, according to the same postmortem. For related coverage, see Bank of England Stablecoin Update Draws Coinbase Response.
Base’s official status page shows the June 25 incident began with investigation at 16:03 UTC, with widespread recovery confirmed at 17:58 UTC. The June 26 incident resumed at 15:47 UTC and was marked resolved at 20:03 UTC. For related coverage, see EBA Crypto Fines Under MiCA: New EU Rules Explained.
Base Build, the project’s official account, stated that both outages were “caused by the same underlying bug in the block builder logic” and confirmed the root cause had been identified and fixed.
On June 25 and 26, Base mainnet experienced two block production outages, both caused by the same underlying bug in the block builder logic.
We’ve identified and fixed the root cause, and have communicated the post mortem to OP chains as feedback.
All funds were safe… pic.twitter.com/eArnK12AgZ
— Base Build (@buildonbase) June 27, 2026
Source: @buildonbase on X
This was not Base’s first block production disruption. The network previously experienced an “unsafe head stall” that interrupted block production earlier this year, raising recurring questions about single-sequencer reliability.
How a stale journal state became the reported root cause
According to the postmortem, the root cause was a sequencer block-building bug that allowed stale journal state to persist after a transaction validation failure. In simpler terms, after one transaction failed validation, outdated internal state was not properly cleared from the system.
That stale state caused a later valid transaction to use an inaccurate gas charge, creating an invalid state transition. Validators rejected this invalid transition, which halted the chain at block 47806542.
The recurrence on June 26 was tied to a separate but related issue: a race condition in the engine reset feature that prevented sequencers from catching up after restart. This race condition slowed mitigation during the first incident and is why the same underlying bug triggered a second outage the next day.
Base noted it had communicated the postmortem findings to other OP Stack chains as feedback, suggesting the bug could potentially affect other rollups built on the same infrastructure.
Why the outages matter for Base users and L2 reliability
Base currently operates as a Stage 1 optimistic rollup securing $10.95 billion in total value secured. Two block production halts in consecutive days on a network of that scale is a material operational event, even when no funds are lost.
The single-sequencer architecture that Base currently uses means one software defect can halt all block production. While Base confirmed all user funds remained safe, the outages prevented any on-chain activity during the affected windows, including trades, transfers, and smart contract interactions.
The incident also underscores broader reliability challenges facing Ethereum layer-2 networks. Coinbase has been expanding its regulatory footprint across multiple jurisdictions, making operational stability on its flagship L2 increasingly important for institutional credibility.
Node operators were required to restart after block 47806542, adding friction to the recovery process beyond simply patching the sequencer.
TLDR Key Points
- Root cause identified: A sequencer block-building bug let stale journal state persist after a transaction validation failure, halting Base mainnet twice in two days.
- Two outages, same bug: The first lasted 116 minutes (June 25) and the second 20 minutes (June 26), with a separate engine reset race condition enabling the recurrence.
- Scale matters: Base secures $10.95 billion in value, making single-sequencer reliability a critical concern for users and the broader OP Stack ecosystem.
Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.
