the coinformer
Contact About
Live 5m

Base chain stalls after invalid block before Beryl upgrade

Base chain stopped producing new blocks before its scheduled Beryl upgrade after the team said a problematic block prevented new blocks from being created.

David Pupăză/Unsplash

Base, Coinbase's Ethereum Layer-2 network, suffered a mainnet chain stall on Thursday after an invalid block interfered with block production.

  • The Base status page first said at 16:03 UTC that mainnet block production was unhealthy and that the team was investigating the issue.
  • By 17:21 UTC, Base said it had isolated a consensus problem that caused an invalid block to be sequenced. That prevented new blocks from being created after block 47806542.
Update June 26. Base announced that Beryl will now activate on mainnet on June 26 at 6pm UTC instead of the previously scheduled June 25 launch.

The chain later began recovering.

  • Base said at 17:51 UTC that sequencing of new blocks had resumed and internal nodes were syncing correctly.
  • At 17:58 UTC, the team said block building had recovered and that ecosystem infrastructure was able to recover syncing. Node runners were told they would need to restart Base nodes to recover syncing.
The timing also collided with a planned network change.
Base mainnet entered scheduled maintenance at 18:00 UTC for the Beryl upgrade, with the window set to run until 20:00 UTC.

Base said node operators must upgrade to version 1.1.1 or higher of the Base software, with preconfigured builds available through the Base node release.

Other 2026 incidents

Base pointed out it still expected the hard fork to activate as planned, while adding that it would share a full postmortem after its root-cause investigation.

The chain stall wasn't Base's first status incident this year. A review of Base's status history and outage trackers shows 13 other non-scheduled incidents in 2026 before Thursday's stall when mainnet, testnet and peering incidents are counted.

A stricter mainnet-related count gives 7 other incidents, including transaction inclusion delays, Flashblocks issues, withdrawal delays, delayed transactions and P2P peering problems.

👀 4