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.
Jun 25, 2026 - 16:52 UTC
Update - We are continuing to investigate this issue.
Jun 25, 2026 - 16:24 UTC
Investigating - Base mainnet block production is currently unhealthy. We're investigating the issue now.
Jun 25, 2026 - 16:03 UTC
Website
Operational
90 days ago
100.0
% uptime
Today
Homepage
Operational
90 days ago
100.0
% uptime
Today
Docs
Operational
90 days ago
100.0
% uptime
Today
Mainnet
Major Outage
90 days ago
99.91
% uptime
Today
Public RPC API
Operational
90 days ago
100.0
% uptime
Today
Deposits
Major Outage
90 days ago
99.97
% uptime
Today
Withdrawals
Partial Outage
90 days ago
99.49
% uptime
Today
Batch submission
Operational
90 days ago
100.0
% uptime
Today
Block production
Major Outage
90 days ago
99.97
% uptime
Today
Flashblocks
Operational
90 days ago
100.0
% uptime
Today
Transaction pool
Operational
90 days ago
100.0
% uptime
Today
Snapshots
Operational
Client Software
Partial Outage
Testnet
Operational
90 days ago
99.98
% uptime
Today
Public RPC API
Operational
90 days ago
100.0
% uptime
Today
Deposits
Operational
90 days ago
100.0
% uptime
Today
Withdrawals
Operational
90 days ago
99.97
% uptime
Today
Batch submission
Operational
90 days ago
100.0
% uptime
Today
Block production
Operational
90 days ago
99.96
% uptime
Today
Flashblocks
Operational
90 days ago
99.98
% uptime
Today
Transaction pool
Operational
90 days ago
100.0
% uptime
Today
Snapshots
Operational
Client Software
Operational
Bridge (Mainnet)
Operational
90 days ago
100.0
% uptime
Today
Bridge (Testnet)
Operational
90 days ago
100.0
% uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Related
No incidents or maintenance related to this downtime.
On Thursday, June 25th at 18:00 UTC (Unix timestamp 1782410400), Base Mainnet will undergo the Beryl upgrade.
Operators of Base Mainnet nodes must upgrade to the 1.1.1, or greater, release of the github.com/base/base software. Preconfigured builds for this version are available from github.com/base/node with a corresponding release: https://github.com/base/node/releases/tag/v1.1.1.
Resolved -
The instability has been addressed and resolved. Node operators who were affected are recommended to upgrade to v1.1.1 of base/base which contains stability improvements and bug fixes: https://github.com/base/base/releases/tag/v1.1.1
Jun 22, 16:35 UTC
Investigating -
Our team is currently investigating degraded broadcasting of Flashblocks on Base mainnet. We believe TX inclusion in final blocks is not affected.
Jun 2, 22:32 UTC
Resolved -
This incident has been resolved.
Jun 22, 16:34 UTC
Identified -
If you find yourself still unable to find peers, please try to delete /$RETH_DATA_FOLDER/discovery-secret file (by default /data if you're using base/node) and restart the node.
Jun 15, 17:59 UTC
Investigating -
We're aware that base mainnet has peering issues for newly started nodes and are actively working on a fix to address that.
For nodes that are struggling to find peers, we recommend adding below cli args to your reth node and restart for now.
Completed -
The scheduled maintenance has been completed.
Jun 18, 20:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 18, 18:00 UTC
Scheduled -
On Thursday, June 18th at 18:00 UTC (Unix timestamp 1781805600), the Base Sepolia Testnet will undergo the Beryl upgrade.
Operators of Base Sepolia Testnet nodes must upgrade to the 1.1.0, or greater, release of the github.com/base/base software. Preconfigured builds for this version are available from github.com/base/node with a corresponding release: https://github.com/base/node/releases/tag/v1.1.0.