Critical incident

Base: Base Mainnet Chain Stall

Affected: Deposits, Withdrawals, Block production, Client Software

Current status of Base: Operational — live Base status

Timeline

1. Jun 25, 2026, 16:03 UTC
   investigating
   Base mainnet block production is currently unhealthy. We're investigating the issue now.
2. Jun 25, 2026, 16:24 UTC
   investigating
   We are continuing to investigate this issue.
3. Jun 25, 2026, 16:52 UTC
   identified
   We have identified the issue with a problematic block interfering with subsequent block building. The team is working on several threads to remediate and we will continue to post updates as soon as we have them.
4. Jun 25, 2026, 17:21 UTC
   identified
   We continue to debug and have isolated a consensus problem that caused an invalid block to be sequenced. This prevented new blocks from being created following block 47806542. Internal sequencer and nodes have preliminarily recovered, the team is working on a fix to resume block propagation to the network while further isolating the root cause of the problematic block.
5. Jun 25, 2026, 17:51 UTC
   identified
   Sequencing of new blocks has resumed and internal nodes are syncing correctly. We continue to investigate the root cause while monitoring internal nodes for stability. For ecosystem node runners - *Base nodes will need to be restarted to recover syncing*. We will continue to investigate and provide updates as we have them.
6. Jun 25, 2026, 17:58 UTC
   monitoring
   We have recovered healthy blockbuilding and confirmed that ecosystem-wide infrastructure is able to recover syncing. We continue monitoring to ensure stability. Notably, we expect the Beryl hardfork to activate as planned at 18:00 UTC. We will continue to investigate the root cause and share a full post-mortem once our investigation concludes.
7. Jun 25, 2026, 19:22 UTC
   monitoring
   Base sequencer and supporting systems remain stable, blocks are being produced normally, and we have verified widespread recovery in the ecosystem. Any remaining Base nodes that are stuck at block 47806542 will recover upon restart and syncing. The team has found the root cause for this halt and is verifying a fix to ensure it cannot recurr. We’ll share a full post mortem including RCA with the ecosystem based on our learnings and fixes as a top priority. We'll continue to monitor all systems to ensure overall network health and stability persists.
8. Jun 26, 2026, 15:33 UTC
   investigating
   Base mainnet block production is currently unhealthy. We're investigating the issue now.
9. Jun 26, 2026, 15:34 UTC
   identified
   Base Mainnet is experiencing a chain halt with the similar symptoms. We're actively working on resuming block production.
10. Jun 26, 2026, 15:47 UTC
    identified
    Block production is resumed. Node operators will need to restart their Base Mainnet nodes in order to resume syncing.
11. Jun 26, 2026, 16:11 UTC
    monitoring
    A fix has been implemented and we are monitoring the results.
12. Jun 26, 2026, 20:03 UTC
    resolved
    Block production has been succesfully progressing for Base Mainnet. A detailed postmortem will be be published to outline the technical root cause.

Updates as published by Base (original).