Coinbase's Base Network Halted for Two Hours by Consensus Failure

Coinbase's Base blockchain halted block production for roughly two hours on Thursday after a consensus problem brought the layer-2 network offline, the project confirmed. Block production subsequently resumed, though the disruption marked one of the more significant operational interruptions the network has faced.

What Went Wrong

Base attributed the outage to a consensus failure — the class of fault in which nodes operating a blockchain cannot agree on the canonical state of the chain and, rather than producing potentially invalid blocks, stop producing blocks altogether. That mechanism is by design a safety feature, but it renders a network functionally unreachable for users and applications while the disagreement persists.

The roughly two-hour window during which Base was offline meant any transaction submitted to the network during that period could not be confirmed, affecting decentralised applications and users relying on the chain for settlement.

Base in Context

Base is Coinbase's own layer-2 network, built on Optimism's OP Stack and settled to Ethereum. Layer-2 chains are designed to handle transaction volume at lower cost than Ethereum's base layer, making their uptime a direct operational concern for the retail and institutional users Coinbase has sought to attract to on-chain activity. An outage on such a network draws attention to the reliability assumptions baked into layer-2 architecture, which, unlike Ethereum itself, depends on a smaller and more concentrated set of sequencer infrastructure.

Recovery and Outstanding Questions

Base said the network returned to normal operation after the interruption. The source does not specify what triggered the underlying consensus disagreement, whether a software fault or node-level issue was responsible, or what steps were taken to restore production. No timeline for a post-mortem was included in the network's initial statement.

For a network positioned as institutional-grade infrastructure, the absence of that detail will likely draw scrutiny. Consensus failures in public blockchains are uncommon but not unprecedented; how quickly and transparently an operator explains the root cause typically determines how the incident is weighed by the developers and protocols building on top of it.

Related reading

• Fidelity Rebuts Bitcoin Security Concerns Tied to Halving Schedule