Base had 24 outages in the last 2 years totaling 2964h 34m of downtime — averaging 1 incident per month.
There were 24 Base outages since August 5, 2025 totaling 2964h 34m of downtime. Each is summarised below — incident details, duration, and resolution information.
Base Mainnet withdrawals are delayed due to a TEE enclave issue that halted proposals. A fix is in progress.
This incident has been resolved.
Base is experiencing an elevated rate of missed blocks. Transactions sent during missed blocks are delayed until the next successful block.
This incident has been resolved.
Latency on https://sepolia.base.org is high due to a node provider upgrade.
We have temporarily decreased rate limits for this endpoint to ease traffic. Latency is moving back to normal on this endpoint.
This incident has been resolved.
There is no outage. This is preemptive in case node operators encounter peering issues. However, upcoming p2p changes may impact peer discovery for Base nodes. If your node encounters p2p issues, please use the script linked here: https://gist.github.com/meyer9/8f15028681045062d59b7521deb19822#file-add-peers-sh
The migration has been completed. It can be difficult to find a peer that isn't full on peers already. We are working with the Reth team to continue improving the ability to find peers.
Base Sepolia Testnet is experiencing an outage in block production. The team is actively investigating.
Block production has resumed on Sepolia testnet.
We are currently investigating this issue. The Sepolia safe head is current stalled. This seems to affect op-node users running with consensus-layer sync mode.
This is now mitigated. Safe head is progress normally for Sepolia Testnet
Flashblocks is currently down for Sepolia Testnet. The team has identified the issue and is rolling out a fix.
This incident has been resolved.
Base Mainnet is currently not producing flashblocks. Normal block production is unaffected. We're actively working to restore flashblock production.
We've identified an issue in our public RPC nodes that caused certain endpoints to not reflect latest flashblock data. Users may have also experienced increased error rates for read endpoints on https://mainnet.base.org/. We're working on implementing a fix.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Users connecting to the Flashblocks websocket (mainnet.flashblocks.base.org) may have trouble connecting and receiving flashblocks. Block production is unaffected. We are currently investigation the issue.
We are monitoring a fix that has been implemented.
This incident has been resolved.
We are currently investigating the issue, blocks are being produced, but with no transaction included.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Base mainnet is experiencing periodically delayed blocks due to volatile activity. We're actively monitoring and working to improve the consistency of block building performance. Between 14:45 and 15:10 UTC on 1/20/2026, users may have noticed delayed transaction inclusion and degraded block building performance .
We are aware of degraded Flashblocks building, resulting in fewer broadcasted Flashblocks than expected. Users may also experience periodic reorgs of Flashblocks.
Flashblocks building performance has has returned to expected values.
We are currently investigating degraded connection stability to the Base Mainnet WebSocket endpoint for Flashblocks `wss://mainnet.flashblocks.base.org/ws`. Applications and nodes may experience intermittent connection drops to that endpoint.
We have identified bottlenecks with the Websocket endpoints distributing Flashblocks. Between Nov 5-10, several changes were made that reduced connection drops by 50%. However, investigation continues in order to further reduce connection instability and lower the latency in receiving messages. Updates will be posted here as progress is made.
We have made improvements to the handling of rate limits in order to provide a more stable endpoint for Flashblocks.
A bug is causing inaccurate data to be returned from `eth_call` requests when used on Flashblock RPCs. This happens only when the ‘pending’ tag is used for `eth_call`. We’re working on a base/node release to fix this as soon as possible.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Base Mainnet is experiencing high RPC and transaction inclusion latencies, as well as periodic inconsistencies in block production times.
Block building and RPC performance has returned to normal
We are investigating a reduction in Base network capacity.
AWS is having a major outage that is affecting Base infrastructure.
The AWS outage has resolved. Batch submission has resumed, and transaction capacity has returned to normal.
Periodic congestion on Base is causing delays in transaction inclusion.
The mempool size has been increased to allow more transactions to be included in blocks quickly during periods of congestion. We will continue to monitor the network for delayed transaction inclusion.
Heavy transaction volume on Base L2 is causing delays in batching data to Ethereum. Node operators may experience node client syncing delays and applications on Base may notice a lagging safe head. Block building (unsafe head) continues to function normally.
The safe head is still lagging behind, and the Base sequencing is currently limiting the amount of calldata it can include in L2 blocks. This is to ensure the safe head can progress on L1. Users may experience delays in transaction inclusion, and potentially a high rate of transaction drops.
This incident has been resolved. Base chain is functioning properly.
Flashblocks were unavailable for ~10 minutes. We've identified the root cause and implemented a fix. We're currently monitoring the situation.
This incident has been resolved.
Base Sepolia Preconf Flashblocks RPC started experiencing downtime at 12:45pm ET. The issue has been identified and we are working to restore service.
A fix has been implemented and we are monitoring the results.
The incident has been resolved.
Base engineering team is aware of an issue causing a halt on the Sepolia testnet. We're working to get block production healthy as soon as possible.
Block building failures have been mitigated. We will continue to monitor the block production health.
This incident has been resolved.