Base, one of Ethereum's largest layer-2 networks by total value locked, went offline for approximately two hours on June 25, according to CoinDesk reporting. The incident stopped all transaction processing on the chain. Coinbase, which operates Base's sequencer, attributed the disruption to infrastructure-related problems but did not immediately disclose specific technical details about what failed or how the issue was resolved.
The outage underscores a structural vulnerability in layer-2 architecture that many rollup operators have yet to solve. Base, like most other rollups currently in production, relies on a single sequencer to order and bundle transactions before posting them to Ethereum. That design choice prioritizes speed and cost over redundancy. If that one sequencer stops responding, the network stops.
Coinbase has published plans to decentralize Base's sequencer, which would distribute ordering authority across multiple parties and eliminate the single point of failure. The roadmap does not yet include a firm date for that transition. Until sequencer decentralization ships, Base users and application developers absorb the risk that maintenance windows, infrastructure failures, or operator mistakes will cause another halt.
Layer-2 networks have become critical infrastructure for Ethereum users. Base alone hosts billions of dollars in total value locked across DeFi protocols, stablecoins, and other applications. Two hours of downtime is a meaningful window for traders and anyone relying on timely settlement. For comparison, Ethereum's base layer targets 12-second block times and has not experienced a network-wide halt in its operational history.
Coinbase did not provide a detailed postmortem at the time of reporting. Operators of other rollups have faced similar incidents in recent years, and the typical response has been a public incident review that walks through the failure mode, mitigation steps taken, and roadmap updates. The expectation from infrastructure-aware users is that Base will follow that pattern.
Sequencer decentralization is not a quick pivot. Most rollup teams estimate the work takes 12 to 18 months from design approval to mainnet deployment. Arbitrum and Optimism, the two largest layer-2 networks, have both committed to the migration but neither has fully shipped it yet. Base's timeline will likely follow a similar arc, meaning single-sequencer risk persists for now.
The incident also illustrates why client diversity and redundancy matter in protocol infrastructure. A network with multiple sequencer implementations or fallback mechanisms might have recovered faster or avoided the outage entirely. Base's engineering roadmap should clarify not just when sequencer decentralization arrives, but what interim safeguards are being deployed.