Coinbase’s (NASDAQ:COIN) Ethereum Layer 2 network Base faced its second significant mainnet technical setback in as many days, with block production stalling again on June 26, 2026, after a similar incident the previous day. The repeated halts briefly disrupted transaction processing and related services across one of the largest scaling solutions on Ethereum.
The first disruption began on June 25 around 16:03 UTC when Base’s status monitoring flagged unhealthy block production.
Engineers quickly traced the problem to a consensus failure in which an invalid block entered the sequencing pipeline.
This prevented the network from building any new blocks beyond block height 47806542.
Block production paused while the team isolated the issue, implemented internal recovery measures, and prepared a fix.
Sequencing of new blocks resumed roughly two hours later, around 17:51 UTC.
Node operators across the ecosystem were advised to restart their Base nodes to resync and catch up with the chain.
By evening, the network had stabilized, and monitoring confirmed healthy block production.
Just over 24 hours later, on June 26 at approximately 15:33 UTC, block production turned unhealthy once more, exhibiting nearly identical symptoms.
The team identified the chain halt and moved swiftly to restore operations. Block production resumed shortly afterward, with another round of node restarts required for full ecosystem recovery.
A fix was deployed, and by 20:03 UTC the incident was marked resolved, with block production progressing normally again.
Throughout both episodes, Base emphasized that user funds remained fully secure and that no assets were at risk.
The disruptions primarily affected transaction throughput, deposits, and withdrawals while the sequencer worked to restore normal block creation.
Many decentralized applications and users experienced temporary delays until the network caught up.
The incidents unfolded alongside Base’s scheduled Beryl hardfork upgrade, which activated on June 25 at 18:00 UTC.
The upgrade itself completed successfully and introduced improvements including a shorter withdrawal period.
Earlier in June, the network had also resolved a separate flashblocks instability issue through a software update.
These back-to-back halts represent a notable period of volatility for Base, which has generally maintained strong uptime since its launch.
The team has stated that a detailed postmortem report will be published soon to outline the precise technical root cause and any steps taken to prevent recurrence.
The rapid identification and resolution of both issues demonstrate the operational responsiveness of the Base engineering team.
However, the recurrence within 24 hours underscores the inherent complexities of maintaining high-performance Layer 2 infrastructure, even for well-resourced projects. Users and developers are encouraged to monitor official channels for the upcoming postmortem and any further guidance on node operations. As of the latest updates, Base mainnet is operating normally.