Base Confirms 33-Minute Disruption on August 5
Base has confirmed it experienced a 33-minute disruption on August 5, halting block production on its mainnet. The disruption occurred when Base’s active sequencer fell behind due to high onchain activity.
Details of the 33-Minute Disruption
Base, the Ethereum Layer 2 network developed by Coinbase, confirmed that a disruption on Aug. 5, which lasted 33 minutes, caused a halt to block production on its mainnet. The confirmation came hours after social media reports that the mainnet had stalled at block 33,792,704 due to an “unsafe head delay.” It was reportedly the first outage for the network since 2023.
In an incident report, Base explained that its active sequencer began to fall behind due to high onchain activity. This was detected by its OP Stack component, Conductor, which then initiated an “automated handoff to a new sequencer.” However, because the new sequencer was “in the process of being provisioned,” no blocks were produced.
The report added, “Typically if an unhealthy sequencer is elected, it does another handoff. Since Conductor was not yet fully enabled on this sequencer, it was unable to initiate another handoff.”
Base’s monitoring systems detected the issue approximately two minutes later, at 11:09 p.m. EST. By 11:12 p.m., the team had begun taking steps to resume block building, including pausing the Conductor. After manually transferring leadership from the unhealthy sequencer to a healthy one, the network was fully recovered by 11:40 p.m.
Reactions and Future Steps
The outage has, unsurprisingly, reignited a long-standing debate and sparked renewed concerns about the fundamental architecture of Base. Critics have been quick to point out the network’s reliance on a single active sequencer for transaction processing as a critical vulnerability. With more than $4.1 billion in total value locked (TVL) within the ecosystem, they argue that this level of centralization represents a single point of failure that fundamentally undermines the principles of decentralized blockchain reliability.
Meanwhile, Base said it has taken steps to prevent a recurrence, including updating its infrastructure “to ensure that when a sequencer is added to the Conductor cluster, it is always able to transfer leadership if elected.” The company also stated that it will test and deploy these fixes as soon as possible to ensure the robustness of its automated systems.