Base Status - Incident History

Base Mainnet proposals halted

Fri, 09 Oct 2026 19:15:21 +0000

Oct 9, 19:15 UTC
Resolved - This incident has been resolved.

Oct 9, 14:21 UTC
Monitoring - We've identified the issue and proposals have resumed.

Oct 9, 13:48 UTC
Update - We are continuing to investigate this issue.

Oct 9, 13:48 UTC
Investigating - The team is investigating the proposal stall. This will slow down in-flight withdrawals.

mainnet.base.org public RPC changes: October 8th, 2026

Thu, 08 Oct 2026 19:42:57 +0000

Oct 8, 19:42 UTC
Completed - The scheduled maintenance has been completed.

Oct 8, 12:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Oct 1, 14:06 UTC
Scheduled - Starting Oct 8, 2026, mainnet.base.org will no longer serve the debug, trace, and txpool namespaces, and read requests will be subject to a lower rate limit. The endpoint remains free and best-effort for basic reads.

Apps that use these namespaces or need higher throughput should move to a dedicated RPC provider before Oct 8. See our supported providers: https://docs.base.org/get-started/base-services-hub#service-providers.

V1 Node Snapshot Deprecation: October 5th, 2026

Tue, 06 Oct 2026 14:00:10 +0000

Oct 6, 14:00 UTC
Completed - The scheduled maintenance has been completed.

Sep 29, 14:55 UTC
Scheduled - Effective Oct 5, 2026: Base will stop publishing V1 node database snapshots. Existing V1 snapshots will no longer be provided past this date.

Download V2 Snapshots here: chain.base.org/snapshots

Instructions: docs.base.org/specifications/node-operators/snapshots

Mainnet: Base Cobalt Upgrade - September 30th

Wed, 30 Sep 2026 20:00:08 +0000

Sep 30, 20:00 UTC
Completed - The scheduled maintenance has been completed.

Sep 30, 18:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Sep 23, 23:00 UTC
Scheduled - On Wednesday, September 30th at 18:00 UTC (Unix timestamp 1790791200), Base Mainnet will undergo the Cobalt upgrade.

Operators of Base Mainnet nodes must upgrade to the 1.4.2, or greater, release of the https://github.com/base/base software (https://github.com/base/base/releases/tag/v1.4.2).

Please note: https://github.com/base/base now hosts the public Base node previously published from base/node. More information can be found here: https://github.com/base/base#run-a-node

For more information on the Cobalt upgrade, please visit our docs: https://docs.base.org/upgrades/cobalt/overview.

Sepolia Testnet: Base Cobalt Upgrade - September 23rd

Wed, 23 Sep 2026 20:00:07 +0000

Sep 23, 20:00 UTC
Completed - The scheduled maintenance has been completed.

Sep 23, 18:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Sep 16, 21:22 UTC
Scheduled - On Wednesday, September 23rd at 18:00 UTC (Unix timestamp 1790186400), the Base Sepolia Testnet will undergo the Cobalt upgrade.

Operators of Base Sepolia Testnet nodes must upgrade to the 1.4.0, or greater, release of the https://github.com/base/base software (https://github.com/base/base/releases/tag/v1.4.0).

Please note: https://github.com/base/base now hosts the public Base node previously published from base/node. More information can be found here: https://github.com/base/base#run-a-node

For more information on the Cobalt upgrade, please visit our docs: https://docs.base.org/upgrades/cobalt/overview.

Base Mainnet Safe head delayed

Tue, 28 Jul 2026 15:13:23 +0000

Jul 28, 15:13 UTC
Resolved - Safe head is progressing normally

Jul 28, 13:10 UTC
Identified - Base Mainnet's Safe head is delayed. New block production is progressing normally; this incident affects only data batching to Ethereum L1.

Reduced Capacity on Base Mainnet Flashblocks Websocket stream

Tue, 21 Jul 2026 19:30:00 +0000

Jul 21, 19:30 UTC
Resolved - Between UTC 19:50 and 20:42, Base Mainnet experienced reduced capacity on the Flashblocks websocket stream. Clients likely experienced delays in receiving messages and rate limits when connecting.

Base Mainnet Chain Stall

Fri, 26 Jun 2026 20:03:41 +0000

Jun 26, 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.

Jun 26, 16:11 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Jun 26, 15:47 UTC
Update - Block production is resumed.

Node operators will need to restart their Base Mainnet nodes in order to resume syncing.

Jun 26, 15:34 UTC
Identified - Base Mainnet is experiencing a chain halt with the similar symptoms. We're actively working on resuming block production.

Jun 26, 15:33 UTC
Investigating - Base mainnet block production is currently unhealthy. We're investigating the issue now.

Jun 25, 19:22 UTC
Update - 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.

Jun 25, 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.

Jun 25, 17:51 UTC
Update - 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.

Jun 25, 17:21 UTC
Update - 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.

Jun 25, 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.

Jun 25, 16:24 UTC
Update - We are continuing to investigate this issue.

Jun 25, 16:03 UTC
Investigating - Base mainnet block production is currently unhealthy. We're investigating the issue now.

Mainnet: Base Beryl Upgrade - June 25th

Thu, 25 Jun 2026 20:00:13 +0000

Jun 25, 20:00 UTC
Completed - The scheduled maintenance has been completed.

Jun 25, 18:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Jun 19, 00:33 UTC
Scheduled - 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.

Please see the following document for migration instructions: https://docs.base.org/base-chain/specs/upgrades/beryl/overview#required-software.

Base Mainnet Periodic Flashblocks Instability

Mon, 22 Jun 2026 16:35:05 +0000

Jun 22, 16:35 UTC
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 2, 22:32 UTC
Investigating - Our team is currently investigating degraded broadcasting of Flashblocks on Base mainnet. We believe TX inclusion in final blocks is not affected.

Base Mainnet p2p peering stability

Mon, 22 Jun 2026 16:34:04 +0000

Jun 22, 16:34 UTC
Resolved - This incident has been resolved.

Jun 15, 17:59 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 12, 21:28 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.

```
--trusted-peers enode://674db972a48b9cab934407c9e28c50fb3c95719272d314dd408ef82804796e06e5de6f991db4e9f33b2b0f09f1ddf3d91f59cd6b3f4b183052efc3d88455d5ac@13.221.49.63:30303?discport=30304,enode://174bcf56adbfbd8eb6fa1e680c356a495d4a4dd638ede1187846f748bf85a9a7396feb64bcd8e725509efdf85362928b71ac50ad59fd73f44aad7103c56e94ac@54.161.193.150:30303?discport=30304,enode://0d5988e13d93d7b96f89767d64445d0b03ca1ad1d7e17a19c60e0997a3bb27217d8f0fca3353abb051bf2b10b10be73d4c2250a15cc1f9e3d8dd5b770fadaf38@54.209.136.129:30303?discport=30304,enode://843e9e53a61bee5bf6f7c2739455ed61ef1056172812123a3f7d6f3f10d12f7c0dc8d7a4bda966ddd4a1d1b61d58bff5558f924b3f0ca84e9e8c0e6feb277142@98.80.147.106:30303?discport=30304,enode://3f4dba3d8b19727f942c0dd63b9d5a2c87aa5cf175bd6a86b78d7913950333382f3befc09f7c0e6af36451091f5d031b2d6db2996480b5c261812ddd76708524@3.81.131.168:30303?discport=30304,enode://3081267a138669585724beec40a422f5f2c8e7f050c5845936420e679c48b43e413106c220b6aa8cd9636042962f2b2ab02e3701f6d8d9233075061cafcfe3b6@34.203.10.78:30303?discport=30304
```

Sepolia Testnet: Base Beryl Upgrade - June 18th

Thu, 18 Jun 2026 20:00:07 +0000

Jun 18, 20:00 UTC
Completed - The scheduled maintenance has been completed.

Jun 18, 18:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Jun 12, 20:48 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.

Please see the following document for migration instructions: https://docs.base.org/base-chain/specs/upgrades/beryl/overview#required-software

Node Peering Stability on Base Testnet and Mainnet

Thu, 04 Jun 2026 19:42:05 +0000

Jun 4, 19:42 UTC
Resolved - The discv5 protocol ID 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.

https://docs.base.org/base-chain/specs/upgrades/azul/exec-engine#discovery-protocol-now-uses-basev0-protcol-id

Apr 30, 21:14 UTC
Monitoring - 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

Base Mainnet Withdrawal Delay

Sun, 31 May 2026 03:38:45 +0000

May 31, 03:38 UTC
Resolved - This incident has been resolved.

May 29, 15:55 UTC
Identified - Base Mainnet withdrawals are delayed due to a TEE enclave issue that halted proposals. A fix is in progress.

Mainnet: Base Azul Upgrade - May 28th

Thu, 28 May 2026 20:00:10 +0000

May 28, 20:00 UTC
Completed - The scheduled maintenance has been completed.

May 28, 18:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

May 22, 16:24 UTC
Scheduled - On Thursday, May 28th at 18:00 UTC (Unix timestamp 1779991200), Base Mainnet will undergo the Azul upgrade.

Operators of Base Mainnet nodes must upgrade to the 0.9.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/v0.16.0.

NOTE
It is mandatory that nodes run base-consensus and base-reth-node binaries. Op-geth and op-node clients are no longer supported. This upgrade will also invalidate pending withdrawals. As seen in previous upgrades, users will need to submit a second proof transaction post-upgrade to complete withdrawals if they are still pending.

Please see the following document for migration instructions: https://docs.base.org/base-chain/node-operators/base-v1-upgrade.

Delayed Transactions

Thu, 14 May 2026 05:04:08 +0000

May 14, 05:04 UTC
Resolved - This incident has been resolved.

May 13, 16:44 UTC
Investigating - Base is experiencing an elevated rate of missed blocks. Transactions sent during missed blocks are delayed until the next successful block.

Elevated latency on Sepolia RPC

Wed, 13 May 2026 16:52:41 +0000

May 13, 16:52 UTC
Resolved - This incident has been resolved.

May 10, 19:03 UTC
Monitoring - We have temporarily decreased rate limits for this endpoint to ease traffic. Latency is moving back to normal on this endpoint.

May 10, 18:31 UTC
Identified - Latency on https://sepolia.base.org is high due to a node provider upgrade.

Mainnet RPC Upgrade

Tue, 21 Apr 2026 17:36:02 +0000

Apr 21, 17:36 UTC
Completed - The scheduled maintenance has been completed.

Apr 21, 17:27 UTC
Verifying - Verification is currently underway for the maintenance items.

Apr 21, 17:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Apr 16, 15:10 UTC
Scheduled - We will be upgrading the mainnet RPC endpoints (https://mainnet.base.org) to point at a different set of nodes. There should be minimal disruption, however you may notice some requests are cancelled for a short period of time.

Sepolia Testnet: Base Upgrade v1 - April 20th

Mon, 20 Apr 2026 18:00:07 +0000

Apr 20, 18:00 UTC
Completed - The scheduled maintenance has been completed.

Apr 20, 16:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Apr 8, 18:49 UTC
Scheduled - On Monday April 20th between 16:00 and 18:00 UTC, the Base Sepolia Testnet will undergo the v1 upgrade.

Operators of Base Sepolia Testnet nodes must upgrade to the 0.7.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/v0.15.0.

NOTE
It is mandatory that nodes run base-consensus and base-reth-node binaries. Op-geth and op-node clients are no longer supported.

Please see the following document for migration instructions: https://docs.base.org/base-chain/node-operators/base-v1-upgrade

Sepolia Testnet Unsafe Head Stalled

Thu, 16 Apr 2026 19:15:27 +0000

Apr 16, 19:15 UTC
Resolved - Block production has resumed on Sepolia testnet.

Apr 16, 18:26 UTC
Investigating - Base Sepolia Testnet is experiencing an outage in block production. The team is actively investigating.

Sepolia safe head delayed

Sat, 11 Apr 2026 00:45:01 +0000

Apr 11, 00:45 UTC
Resolved - This is now mitigated. Safe head is progress normally for Sepolia Testnet

Apr 10, 22:54 UTC
Investigating - 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.

Sepolia Testnet: Flashblocks down

Tue, 07 Apr 2026 00:55:34 +0000

Apr 7, 00:55 UTC
Resolved - This incident has been resolved.

Apr 7, 00:37 UTC
Identified - Flashblocks is currently down for Sepolia Testnet. The team has identified the issue and is rolling out a fix.

Base Mainnet Flashblocks Degraded

Wed, 01 Apr 2026 13:41:40 +0000

Apr 1, 13:41 UTC
Resolved - This incident has been resolved.

Mar 24, 15:16 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Mar 24, 13:55 UTC
Identified - 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.

Mar 24, 12:00 UTC
Investigating - Base Mainnet is currently not producing flashblocks. Normal block production is unaffected. We're actively working to restore flashblock production.

Base Mainnet Gas Limit Increase from 187.5Mgas/s to 200Mgas/s

Wed, 25 Mar 2026 21:00:07 +0000

Mar 25, 21:00 UTC
Completed - The scheduled maintenance has been completed.

Mar 25, 17:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Mar 24, 21:28 UTC
Scheduled - Base Mainnet gasLimit will increase from 187.5Mgas/s to 200Mgas/s on Wednesday March 25th.

This will be achieved by the following parameter changes:
- Increasing gasLimit to 400_000_000 (this is a per block parameter)
- Decreasing the 1559 elasticity multiplier from 6 to 5
- Decreasing the 1559 denominator from 125 to 100

*NOTE*: This will result in a higher gasTarget, from 62_500_000 to 80_000_000 per block.

Transaction Inclusion Delays

Tue, 24 Mar 2026 13:13:59 +0000

Mar 24, 13:13 UTC
Resolved - Stability of block production and transaction inclusion are back to acceptable levels. We have deployed and confirmed reliability of several improvements to our block builder and transaction processing infrastructure, please reach out in discord with any issues.

Mar 24, 13:12 UTC
Update - Stability of block production and transaction inclusion are back to acceptable levels. We have deployed and confirmed reliability of several improvements to our block builder and transaction processing infrastructure, please reach out in discord with any issues.

Feb 6, 23:48 UTC
Monitoring - We continue to see improved network stability after updating several elements of our routing infrastructure and as overall market volatility has subsided. We will continue monitoring network health and transaction success rate, while working on further upgrades to routing and transaction propagation layers which we described below.

Several larger upgrades are deployed on devnets and testnets to ensure their stability under different network conditions, with plans to promote them to mainnet after we validate their safety. This remains our top priority and we'll continue to post updates with our ongoing progress.

Feb 6, 01:46 UTC
Identified - Update 2/6 01:30 UTC

Overview
We are actively scaling to meet elevated demand. While immediate infrastructure updates are underway to improve current throughput, we have also initiated several longer-term projects to ensure future stability and network performance.

What we did today
We’re landing changes to improve the RPC latency for eth_sendRawTransaction calls during load, and improve the efficiency of getting transactions to the block builder for selection:

* [Live on Mainnet] - Doubled the disk IO throughput of our txpool
* [Live on Mainnet] - Changed our `eth_sendRawTransaction` rate limiting window to smooth out incoming spikes. We will continue changing the rate limiting configuration in the coming days
* Built and tested a more stable routing algorithm for sending transactions to the most efficient backend. We expect this to be on Mainnet within a couple of days

What’s up next
This work is expected to take 4 to 6 weeks. We anticipate this work to achieve stable transaction inclusion and block production
* Implementing a transaction propagation redesign that removes the overhead of P2P when getting transactions to the block builder.
* Optimizing and scaling configurations for `pending` and `queued` storage of transactions
* Unifying the components of our block building, sequencing, and flashblocks streaming

We will share updates here as we make progress.

Feb 5, 15:22 UTC
Update - We are experiencing heavy transaction volume resulting in inclusion delays. Active fixes are in progress

Jan 31, 22:42 UTC
Monitoring - We are actively monitoring network conditions. During periods of high congestion, users may experience intermittent transaction delays or transactions dropped. Submitted transactions can occasionally take up to two minutes to be included in a block or may need to be resubmitted. We are working on longer-term fixes to ameliorate this behavior and will share our plans and updates as we make progress.