A bug in Coinbase’s foundation froze a crucial part of the network’s infrastructure. It has raised new questions about the resilience of Ethereum’s growing Layer-2 ecosystem. However, the issue did not prevent users from sending transactions or communicating with applications on Base.
Blocks were reportedly still being produced and the network appeared to be functioning normally. But behind the scenes, a key component responsible for updating Base’s status on Ether lingered for more than 30 hours. This event was noticed after developers stated that Ether status updates and recordings had been halted.
The base’s 30-hour outage raised concerns about layer 2
Developer donnoh.eth addressed the issue in an X-post. He noted that the glitch went unnoticed because Base withdrawals already require a seven-day challenge period.
He stated, “It’s kind of crazy that base state updates have been unavailable for over 30 hours now due to a bug related to the recent upgrade and no one even noticed, just because withdrawals take seven days anyway.”
According to Base’s status page, the problem was traced to the network’s Trusted Execution Environment (TEE) enclave. The outage prevented the proposal system from generating the status updates needed to anchor Base’s operations back to Ethereum.
The chain continued to process itself and moved transactions normally. Meanwhile, Base’s status stopped updating until the issue was resolved.
In the case of collapses like Base, transitions are performed on L2 before compressed state commitments are periodically posted back to Ether. The TEE helps generate cryptographic certificates. This helps prove that state transitions have been calculated correctly.
This suggests that if that system stops working, users can continue transacting at Layer 2. Meanwhile, the settlement pipeline connecting the network to Ethereum may come to a halt.
No money was lost and the outage left no user assets exposed to theft. But it still temporarily froze one of the key pieces of infrastructure supporting the rollup. It’s critical that this happens, as it happened just a few days after Base deployed the Azul upgrade. It is designed to improve scalability and reportedly increase throughput to as much as 5,000 transactions per second.
Nevertheless, the network faced problems.
Base and Sui face different failure modes
Earlier this year, Base experienced periods of transaction delays during heavy network activity. However, these issues have never stopped settlements. Yet they exposed capacity limitations as usage continued to grow.
Base is not the only one facing this problem. Sui reported a consensus error that disrupted transaction processing for about six hours in January. The network experienced multiple outages related to software bugs introduced during protocol upgrades. It temporarily freezes transfers, DeFi activity, and NFT transactions.
The technology behind these incidents is very different. Basis saw a failure involving a TEE-enabled testing mechanism. On the other hand, Sui’s problems arose from the consensus of the validators and the logic of gas accounting.