TLDR
Base suffered a mainnet outage that disrupted block production.
The issue began around src6:03 UTC, according to Base updates.
Base linked the outage to a problematic block affecting block building.
Deposits, withdrawals and transactions were delayed during the outage.
Base said sequencing resumed and all user funds remained secure.
Coinbase-incubated Ethereum layer-2 network Base resumed block production on Thursday after a mainnet outage interrupted transaction processing, deposits and withdrawals for roughly two hours.
The Base team first reported problems at src6:03 UTC, saying mainnet block production had become unhealthy. The network’s status page later classified the incident as a major outage, with new blocks not being produced reliably and some transactions delayed or stalled.
Base Mainnet is currently halted while the team works on an issue with block production.
All funds are secure, and we’ll update below once resolved.
Appreciate the patience while we get it fixed.
— Base Build (@buildonbase) June 25, 2026
At src6:52 UTC, Base said it had identified a problematic block that was interfering with subsequent block building. The team said it was working on several remediation steps while continuing to provide updates through its public channels.
Problematic Block Disrupts Base Mainnet
Base said the issue was linked to a problematic block that prevented normal block production from continuing. The incident affected sequencing of new blocks and temporarily disrupted the network’s ability to process activity across apps and infrastructure providers.
During the outage, Base told users that all funds remained secure. The network did not initially disclose whether the block issue was caused by a software bug, a consensus fault or another technical problem.
The disruption affected one of Ethereum’s most active layer-2 networks. Base, developed with support from Coinbase, is widely used for decentralized applications, stablecoin transfers, trading platforms and consumer-focused crypto apps.
The incident occurred on the same day as Base’s scheduled Beryl upgrade, which had been planned for src8:00 UTC. Available status updates did not confirm that the outage was related to the planned maintenance.
Sequencing Resumes After Two-Hour Disruption
Base later said sequencing of new blocks had resumed and internal nodes were syncing correctly. The team advised app teams and infrastructure providers running Base nodes to restart them so they could resume syncing blocks from the sequencer.
After block production restarted, Base said apps and infrastructure were beginning to come back online as node operators restarted and resynced their systems. The team said recovery should be quick for each provider once node restarts were initiated.
The outage temporarily halted transaction processing across the network, meaning users may have experienced stalled transactions, delayed deposits and delayed withdrawals until infrastructure providers restored synchronization.
Base said it would continue monitoring network stability and investigating the root cause. The team also repeated that user funds remained secure while the chain recovered.
Outage Adds Focus to Layer-2 Reliability
The incident drew attention to reliability risks across Ethereum layer-2 networks, which depend on sequencers, node operators and application infrastructure to provide low-cost transaction processing at scale.
Base has become one of the largest Ethereum scaling networks by activity, making short outages more visible to users and developers. A block production halt can affect decentralized exchanges, wallets, bridges, payments, lending apps and other on-chain services built on the network.
This was not the first outage reported by Base. The network also experienced a disruption in August 2025, which placed operational resilience and recovery procedures under scrutiny as activity on the chain expanded.
Base’s latest recovery depended partly on node operators restarting their infrastructure after sequencing resumed. That step shows how network restoration can require coordination between the core development team and external service providers that support apps, RPC access, indexing and transaction routing.
The Base team has not yet published a full post-incident report. Further details are expected to focus on the problematic block, the reason it interfered with later block building and any changes needed to prevent a similar interruption.
No responses yet