Base, Coinbase's layer-2 blockchain, went down. Then it came back. Then it went down again. The post-mortem is out and the cause has been identified: a race condition in the sequencer that prevented recovery after the first reset. The second outage was caused by the fix for the first one.
That sequence of events - fix triggers new failure - is a software engineering problem so classic it has a name. But when it happens to a blockchain that billions of dollars move through, the stakes of a bad recovery procedure are different to a bug in a web app.
What a race condition actually is
A race condition occurs when a system's behaviour depends on the timing of multiple operations running simultaneously, and those operations complete in an unexpected order. In Base's case: after the sequencer was reset to address the first outage, the recovery process itself was racing against system state that had not fully stabilised. The sequencer could not catch up. The network went down again.
The post-mortem language - "race condition after the system was reset prevented the sequencers from catching up" - is accurate and appropriately technical without being evasive. Coinbase is not hiding what happened. The transparency is the right call.
The infrastructure credibility question
Every major L2 outage triggers the same debate: can you really call something decentralised infrastructure if a single sequencer going down takes the whole network offline?
Base, like most L2s at this stage, depends on a centralised sequencer to order transactions before they are submitted to Ethereum mainnet. That is a known architectural compromise made in exchange for speed and cost savings. The trade-off is that sequencer failures are network failures.
The Coinbase team has fixed the immediate issue. The longer question - when and how L2 sequencers become genuinely decentralised - remains open across the entire space.
Our take: Base got the post-mortem right. The technical transparency is good. The underlying sequencer architecture question is one the whole L2 ecosystem needs to answer eventually.