Base mainnet outage strikes on upgrade day, halting deposits

Something went wrong inside Base’s blockchain on June 25 — and it wasn’t a minor hiccup. The Base mainnet outage froze block production entirely, cutting off deposits, withdrawals, and client software operations at once, in one of the more disruptive incidents the Coinbase-incubated Layer 2 network has faced.

Key takeaways

• A consensus issue caused an invalid block to be sequenced on Base, halting all new block production after block 47806542.
• Mainnet deposits, withdrawals, block production, and client software were all disrupted during the incident.
• The internal sequencer and nodes have partially recovered, but full block propagation has not yet been restored.
• The root cause of the consensus issue remains under active investigation by the Base team.
• Coinbase users reported experiencing transaction delays on the Base network as a result of the outage.

Consensus Issue Causes Mainnet Stall

The chain stopped moving at a very specific point. Base identified a consensus issue that caused an invalid block to enter the sequencing pipeline — and once that block landed, the network could not produce new blocks beyond block 47806542. Everything after that number simply didn’t exist on the chain.

In blockchain architecture, a consensus issue of this type is particularly disruptive because it doesn’t just slow things down — it creates a hard stop. Nodes that disagreed on the validity of that block couldn’t reconcile and move forward, effectively freezing the chain’s tip. The sequencer, responsible for ordering and submitting transactions to the network, found itself unable to advance past the problematic block.

What makes this significant is the timing. Base had just scheduled its second major network upgrade, called Beryl — which introduces the B20 native token standard and cuts Ethereum withdrawal delays from seven to five days — for June 25 mainnet activation. The stall hit on that same date, making it a particularly unwelcome disruption during what was meant to be a milestone moment for the network.

Impact on Mainnet Operations

The operational damage was broad. Mainnet deposits and withdrawals were disrupted, meaning users could not move funds into or out of the network normally. Block production stopped, which effectively froze on-chain state. Client software was also affected, meaning node operators and developers relying on Base’s infrastructure faced compounding issues beyond just the chain itself.

Coinbase users specifically reported experiencing transaction delays on the Base network, according to reports circulating at the time. For a Layer 2 designed to bring fast, low-cost Ethereum transactions to a broader audience, a complete halt in block production is about as serious as it gets at the infrastructure level.

The breadth of the impact — touching deposits, withdrawals, block production, and client software simultaneously — reflects how deeply a sequencer-level or consensus-level failure can ripple through a Layer 2 stack. Unlike a simple smart contract bug, this kind of issue sits closer to the core of how the network functions.

Recovery Efforts and Current Status

The Base team moved quickly. The internal sequencer and nodes have partially recovered, stabilizing part of the network’s infrastructure. But partial recovery is not full recovery — work to restore complete block propagation was still ongoing at the time of reporting, and the team had not yet provided a timeline for when the network would return to normal operations.

Crucially, the root cause of the consensus issue has not been identified with certainty. The team confirmed it is actively investigating what triggered the invalid block to enter the sequence in the first place. Until that question is answered, the risk of a similar disruption cannot be fully ruled out.

This is the part that will matter most to developers and users building on Base. A partial recovery buys time, but the unresolved investigation means the network is operating with an open question at its technical foundation. How quickly and transparently Base resolves that question will shape how the broader ecosystem judges the incident — and whether confidence in the chain’s reliability holds steady.

FAQ

What caused the Base mainnet block production to stop?

Base identified a consensus issue that caused an invalid block to be sequenced, which prevented new blocks from being produced after block 47806542.

Which mainnet functions were affected by the outage?

The outage disrupted mainnet deposits, withdrawals, block production, and client software operations.

Has the Base network recovered from the stall?

The internal sequencer and nodes have partially recovered, but work is ongoing to restore full block propagation.

Is the cause of the consensus issue known?

No. The root cause of the consensus issue is still under investigation by the Base team.

Article produced with the assistance of artificial intelligence and reviewed by the editorial team.