Base network experienced a two-hour outage, with invalid blocks causing consensus failure.

Coinbase's Ethereum L2 network Base suffered a service outage on June 25, caused by an invalid block entering the sequencing process, triggering consensus failure, blocking subsequent block generation, and halting all on-chain transactions. The Base team identified the root cause 50 minutes after the initial report of the issue, and announced widespread ecosystem recovery approximately two hours later; Base stated that user funds are safe and prioritized post-mortem analysis.

Base Network Affected, Widespread Ecosystem Recovery After About Two Hours

Base網絡中斷公告 (Source: Base)

The Base network status page showed mainnet block production as 'abnormal' at 16:03 UTC. The Base team then made an external announcement and posted on X at around 12:20 PM ET: 'Base mainnet is currently paused. The team is working on block production issues. All funds are safe.'

50 minutes after the initial report (16:52 UTC), Base had identified the root cause of the network outage—an invalid block had entered the sequencing process, preventing subsequent block generation. Base operates as a single sequencer under a rollup architecture, and such consensus issues cause the entire network to stop producing new blocks until the team takes action.

Approximately two hours later, Base announced that 'the ecosystem has been widely restored' and recommended that node operators restart their nodes to facilitate synchronization. After the recovery, Base stated on X: 'The team has identified the root cause of this outage. A comprehensive post-mortem will be conducted as a top priority.'

This Outage Is Base Mainnet's First Block Production Halt in 90 Days; May Saw an Approximately 30-Hour Withdrawal Issue

The Base network status page records this as the first block production stoppage on Base mainnet in 90 days. Looking back at previous records, Base network experienced a withdrawal issue lasting about 30 hours in May 2026, and another outage in August 2025. Coinbase stock COIN fell more than 5% in the previous trading session, trading at approximately $142.52.

Outage Occurred Hours Before Planned Beryl Hard Fork Upgrade

This outage occurred hours before the originally scheduled Beryl hard fork upgrade. The Beryl upgrade will introduce new token standards for the Base network, with specific applications including stablecoins and tokenized real-world assets (RWA). Base did not indicate a direct link between this outage and the Beryl upgrade plan.

Frequently Asked Questions

What is the root cause of the Coinbase Base outage?

According to the Base network status page, the root cause of the outage was an invalid block entering the sequencing process, triggering consensus failure and preventing subsequent block generation. Base operates as a single sequencer under a rollup architecture; such consensus issues cause the entire chain to halt until the team identifies and resolves the issue.

What is the timeline and recovery process of this service outage?

The network was affected at 16:03 UTC; Base announced the outage on X at around 12:20 PM ET; at 16:52 UTC (50 minutes after initial report) Base had identified the root cause; approximately two hours later announced widespread ecosystem recovery. Base stated throughout that user funds were safe and committed to a comprehensive post-mortem.

What is the Beryl hard fork, and what is its temporal relationship to this outage?

Beryl is a hard fork upgrade for the Base network, planned to occur within hours after this outage began. It will introduce new token standards supporting new applications for stablecoins and tokenized real-world assets (RWA). This outage occurred hours before the planned upgrade, but Base has not disclosed a direct connection between the two.

Disclaimer: The information on this page may come from third-party sources and is for reference only. It does not represent the views or opinions of Gate and does not constitute any financial, investment, or legal advice. Virtual asset trading involves high risk. Please do not rely solely on the information on this page when making decisions. For details, see the Disclaimer.
Comment
0/400
No comments