Base network's mainnet block production stalled for nearly two hours on June 25, 2026, after block #47,806,542 triggered a consensus failure that froze the sequencer at 16:03 UTC. The invalid block prevented all subsequent block building in what Base engineers classified as an "unsafe head stall," where the sequencer stopped advancing new blocks before they could be posted to Ethereum's layer one for finalization. Coinbase's Base team identified the root cause by 16:52 UTC and restored sequencing by 17:51 UTC, confirming all user funds remained safe throughout the incident. The stall occurred on the same day as Base's scheduled Beryl hard fork activation at 18:00 UTC, though the team confirmed the two events were unrelated. Base operates as a layer-2 network built on the OP Stack framework, where sequencers produce blocks that are later batched and submitted to Ethereum for final settlement.
Base Engineers Isolate Block #47,806,542 as Consensus Failure Source
Base engineers detected unhealthy block production at 16:03 UTC on June 25, 2026. By 16:52 UTC, the team identified block #47,806,542 as the source of the consensus problem that caused the sequencer to produce an invalid block. The invalid block interfered with all subsequent block building, creating what OP Stack terminology classifies as an "unsafe head stall." The unsafe head refers to the latest sequencer-produced blocks that have not yet been posted to Ethereum's layer one for finalization.
The incident timeline proceeded as follows: At 16:03 UTC, block production was flagged as unhealthy and investigation began. At 16:52 UTC, engineers identified block #47,806,542 as the problematic source. At 17:21 UTC, the consensus issue was isolated and internal sequencer and nodes showed preliminary recovery. At 17:51 UTC, block sequencing resumed and internal nodes began syncing correctly. At 17:58 UTC, blockbuilding was confirmed healthy and the network entered monitoring phase.
Deposits and Transactions Delayed During Two-Hour Stall
Deposits, withdrawals, and transactions on Base were delayed during the roughly two-hour stall. The Base team confirmed funds are not at risk. Unsafe head stalls occur before blocks are batched and submitted to Ethereum L1, so there is no exposure to permanent loss or meaningful chain reorganizations.
Node operators running Base infrastructure will need to restart their nodes to fully recover syncing. The status page at status.base.org and block explorer basescan.org remain the primary monitoring resources.
Beryl Hard Fork Proceeds on Schedule Despite Sequencer Issue
The incident coincided with the scheduled Beryl hard fork, planned for an 18:00 UTC activation window on June 25. Base confirmed the stall is unrelated to the upgrade.
Beryl introduces B20, a native token standard built directly into node software rather than deployed as a smart contract, making token issuance more efficient for stablecoins and real-world asset projects. The upgrade also reduces withdrawal delays and ships Reth V2 improvements. Node operators must run base/node v1.1.1 or later. Most users and existing contracts require no action.
Base Team Plans Post-Mortem Publication After Root Cause Review
Base engineers are continuing to investigate the root cause of the invalid block and plan to publish a full post-mortem once the review concludes. Unsafe head stalls of this type have occurred previously on other layer two networks and Optimism mainnet, often tied to internal infrastructure conditions, L1 node issues, or load-related factors. This incident lasted roughly 115 minutes before sequencing resumed.
FAQ
What caused Base network to stop producing blocks on June 25?
Block #47,806,542 caused a consensus failure that froze Base's sequencer at 16:03 UTC on June 25, 2026. The invalid block prevented all subsequent block building in what engineers classified as an "unsafe head stall." Base's team identified the problematic block by 16:52 UTC and restored sequencing by 17:51 UTC, with blockbuilding confirmed healthy by 17:58 UTC.
Are funds safe after the Base network stall?
Coinbase's Base team confirmed all funds are safe. Unsafe head stalls occur before blocks are batched and submitted to Ethereum's layer one for finalization, so there is no exposure to permanent loss or meaningful chain reorganizations. Deposits, withdrawals, and transactions were delayed during the roughly two-hour stall but no funds were at risk.
Did the Base network stall affect the Beryl hard fork activation?
Base confirmed the stall is unrelated to the Beryl upgrade. The Beryl hard fork remained on schedule for its 18:00 UTC activation window on June 25, the same day as the sequencer incident. Beryl introduces the B20 native token standard and requires node operators to run base/node v1.1.1 or later, but most users and existing contracts require no action.
