Base Blockchain Resumes After Two-Hour Outage That Halted Block Production

• Base restored normal operations after a nearly two-hour consensus-related outage halted block production.
• Transaction submissions continued during the disruption, but confirmations were delayed until the network resumed.
• Coinbase and Base developers identified the issue, implemented a fix, and confirmed the network was fully operational.
• The incident marks one of the network’s most significant interruptions since Base launched its mainnet in 2023.

Base resumes block production after consensus-related outage

Coinbase-backed Ethereum Layer 2 network Base has fully restored operations after a consensus-related issue temporarily halted block production for nearly two hours, disrupting transaction confirmations across the network.

The interruption began on June 25, when Base validators stopped producing new blocks due to what the development team described as a consensus fault. Although users were still able to submit transactions, they remained pending because no new blocks were being finalized during the outage.

Base first reported degraded block production on its official status page at 4:03 p.m. UTC. The team later determined that a consensus issue had resulted in an invalid block being sequenced, causing block production to stop after block 47,806,542.

Base developers acknowledged the incident shortly after it began and initiated an investigation. The team later deployed a network fix, allowing block production to resume. Following the restoration, developers confirmed that the blockchain was processing transactions normally and that pending transactions were being finalized.

According to the project’s status updates, the network was fully operational after approximately two hours of downtime.

Developers identify and resolve the network issue

The Base team stated that the disruption originated from a consensus-related problem affecting block production rather than an external attack or security breach. Engineers worked to isolate the fault before implementing a corrective update that restored consensus across the validator network.

Following the recovery, the team said it would continue monitoring the network to ensure stability while conducting a post-incident review to determine the precise technical cause of the outage.

In a separate update published on June 26, a Base creator Jesse Pollak said the team had identified and patched the root cause of the chain halt and reiterated that a full post-mortem would be released. The developer also said all user funds remained safe throughout the incident, while acknowledging that “a halt is not okay” and that the team would use the experience to further strengthen Base as a platform for global, 24/7 finance.

During the disruption, decentralized applications built on Base experienced delayed transaction confirmations because new blocks were temporarily unavailable. However, once block production resumed, the network gradually processed the accumulated transaction backlog.

Outage highlights infrastructure reliability as Base continues to expand

The latest disruption follows a previous outage in August 2025, when Base experienced a 33-minute interruption after a sequencer handoff issue halted block production. Following that incident, the development team introduced infrastructure improvements and additional testing aimed at strengthening network reliability.

The incident follows Coinbase’s recent six-hour trading platform outage, drawing renewed attention to the resilience of its broader ecosystem. It also comes after Sui’s recent network instability, with the blockchain experiencing three mainnet outages within two days after its v1.72 upgrade, raising broader concerns over blockchain infrastructure reliability.

While blockchain networks occasionally experience temporary technical interruptions, prolonged pauses in block production remain relatively uncommon for major Layer 2 networks. The latest outage highlights the importance of consensus reliability as Base continues to process growing transaction volumes and support an expanding ecosystem of applications.

The development team has indicated that additional technical details will be shared following a complete post-mortem review of the incident. At the time of publication, the network remained operational and block production had returned to normal.