On June 25, Coinbase’s Ethereum Layer-2 network Base experienced a major mainnet stall that halted block production and disrupted normal operations.
Blocks are being produced normally, and we have verified widespread recovery in the ecosystem.
Any remaining stuck Base nodes will recover upon restart and syncing.
The team has found the root cause for this halt and we’ll share a full post mortem based on our learnings and…
— Base Build (@buildonbase) June 25, 2026
According to the data, the incident started around 16:03 UTC when the network’s status page reported unhealthy production. This issue was sparked by a problematic block that caused a consensus issue and prevented new blocks from being built. “We have identified the issue with a problematic block interfering with subsequent block building,” stated in the official status page.
The outage lasted around 2 hours, with block sequencing resuming around 17:58 UTC, and full ecosystem recovery required restarts for some operators. The team confirmed that the Beryl upgrade proceeded as scheduled at 18:00 UTC during the monitoring phase.
Base Network Suffers Major Mainnet Stall
On the Base network, users have faced abrupt disruptions as transactions stopped confirming. This has created major issues on the network, including stuck swaps, failed interactions in DeFi apps, delayed deposits, and halted withdrawals.
The issue has sparked panic in the Base community as many users were reporting pending transactions, liquidity providers, and dApp users experiencing errors or timeouts.
After the issue came into the light, Base Build has immediately shared a post on the post on X, saying that, “Base Mainnet is currently halted while the team works on an issue with block production. All funds are secure, and we’ll update below once resolved. Appreciate the patience while we get it fixed.”
What Caused the Base Network Halt?
In the official update, the Base team mentioned that the problematic block interfered with building and confirmed partial recovery of the internal sequencer and nodes. In order to resolve the issue, the team has isolated the consensus issue and asked node operators to restart for syncing.
“We continue to debug and have isolated a consensus problem that caused an invalid block to be sequenced. This prevented new blocks from being created following block 47806542. Internal sequencer and nodes have preliminarily recovered, the team is working on a fix to resume block propagation to the network while further isolating the root cause of the problematic block,” mentioned in the official status update.
Base Network Fully Recovers Operations
As per the latest announcement, the Base team has successfully recovered healthy blockbuilding. The sequencing of new blocks has been resumed. Apart from this, nodes on the network are in perfect sync. The network entered the monitoring phase, with the Beryl upgrade activation time. Beryl introduces the B20 token standard for the issuance of stablecoins and real-world assets.
Even after restoring the operation to normal condition, the team is still monitoring all systems in order to ensure that the network stays healthy. They have also claimed to identify the root cause of the halt.
“The team has found the root cause for this halt and is verifying a fix to ensure it cannot recurr. We’ll share a full post mortem including RCA with the ecosystem based on our learnings and fixes as a top priority. We’ll continue to monitor all systems to ensure overall network health and stability persists,” stated in the latest update.
In the last few months, there have been many networks that have suffered outages or other node-related issues. In May, Sui Mainnet experienced multiple outages, including three network halts in just 2 days. These outages were linked to bugs in the v1.72 software upgrade. This bug has created major issues on the network, such as gas charging logic errors. Validators on the network have also experienced crashes.
On June 3, the Zcash mainnet witnessed a major disruption where block production stopped for more than 4 hours. The outage has taken place after Zcash developers executed an emergency soft fork to fix a 4-year-old bug in the Orchard shielded pool.
