Skip to content
BaseHub by Will Binns Updated

Network Incident History

A running log of substantive incidents and scheduled upgrades affecting Base Mainnet and Base Sepolia. Procedural status pings are omitted. Entries are newest first.

2026-11-17 — Empty blocks slow Sepolia inclusion (resolved)

Section titled “2026-11-17 — Empty blocks slow Sepolia inclusion (resolved)”

At 19:53 UTC on November 17, the team reported that Base Sepolia was producing an unusually large share of empty blocks, so testnet transactions took longer than normal to land. The cause was identified and the incident was marked resolved at 20:30 UTC, roughly 40 minutes later. Mainnet was not part of the report. Status page

2026-11-05 — v1.5.3 patches a state root risk (completed)

Section titled “2026-11-05 — v1.5.3 patches a state root risk (completed)”

On November 4, a bug turned up in Reth that could, in rare cases, lead a node to compute the wrong state root. The upstream fix is paradigmxyz/reth#28264. Because Base runs on Reth, the team applied the same mitigation to every block builder that day, so no new block was exposed. They also recomputed the chain’s state root and found it correct, and noted that the proof system checks every state root with an independent implementation and would have flagged a mismatch. No user was affected. Base posted the notice on November 5 at 16:18 UTC and published v1.5.3 at 16:19 UTC. That release stops a validator from halting when it meets an invalid state root. Base recommends that every operator upgrade to it; no resync or other step is needed. The maintenance closed on November 7 at 16:19 UTC.

2026-11-05 — Mainnet Denim upgrade (completed)

Section titled “2026-11-05 — Mainnet Denim upgrade (completed)”

Base posted the schedule on October 30 at 22:16 UTC: Mainnet would take the Denim hardfork on Thursday, November 5 at 18:00 UTC (Unix timestamp 1793901600) and stay up through the window. Operators had to run v1.5.1 of base/base, and anyone coming from an older release had to drop --enable-experimental-validity-transactions from base-reth-node first or the node would not start. Denim went live on time. At 18:14 UTC Base confirmed activation and said it was looking into periodic delays in transaction inclusion, which left more empty blocks than expected. The notice closed on November 9 at 19:45 UTC with all systems reported stable. See the Denim overview.

2026-11-02 — Slow transaction inclusion on Mainnet (resolved)

Section titled “2026-11-02 — Slow transaction inclusion on Mainnet (resolved)”

At 13:36 UTC on November 2, Base began looking into reports that Mainnet transactions were taking longer than usual to reach a block or a preconfirmation. Blocks kept coming at the normal pace. An hour later the team had found a performance problem and pushed optimizations; a fix was in place and under watch by 14:55 UTC. The incident was formally closed on November 9 at 20:08 UTC.

2026-10-29 — Slow transaction inclusion on Mainnet (resolved)

Section titled “2026-10-29 — Slow transaction inclusion on Mainnet (resolved)”

Base opened an investigation at 16:34 UTC on October 29 after reports of slow inclusion on Mainnet. Block production stayed normal throughout. A fix went out and early monitoring looked clean by October 30 at 19:28 UTC, and the incident closed on October 31 at 16:37 UTC.

2026-10-24 — Mempool congestion delays transactions (resolved)

Section titled “2026-10-24 — Mempool congestion delays transactions (resolved)”

Posted after the fact, on October 24 at 12:30 UTC: an unexpected build-up in the mempool caused some transactions to be delayed, and some were dropped from the mempool outright. The status page gives no network label, start time, or duration.

2026-10-23 — Slow Sepolia public RPC (resolved)

Section titled “2026-10-23 — Slow Sepolia public RPC (resolved)”

The public Base Sepolia RPC answered slowly in the early hours of October 23. Base had identified the cause by 04:58 UTC, deployed a fix by 05:04 UTC, and closed the incident at 06:00 UTC.

2026-10-21 — Sepolia Denim upgrade (completed)

Section titled “2026-10-21 — Sepolia Denim upgrade (completed)”

The window opened on schedule at 18:00 UTC, and Base marked it complete at 18:50 UTC with Denim active on Base Sepolia.

Base Sepolia is set to activate the Denim hardfork on Wednesday, October 21st at 18:00 UTC (Unix timestamp 1792605600), inside a maintenance window that runs until 20:00 UTC. The notice went up on October 19 at 13:52 UTC, and the testnet is expected to keep running through the upgrade. Sepolia node operators need v1.5.0 of github.com/base/base or a later release. The notice also calls out a startup trap: v1.5.0 no longer knows --enable-experimental-validity-transactions, so a base-reth-node launched with that flag will not start until the flag is removed (the builder twin, --builder.enable-experimental-validity-transactions, is gone too). See the Denim overview for what the fork changes.

2026-10-09 — Mainnet output proposals stalled (resolved)

Section titled “2026-10-09 — Mainnet output proposals stalled (resolved)”

The status page opened an incident at 13:48 UTC on Friday, October 9th: new output proposals for Base Mainnet had stopped, which holds up withdrawals already in flight. Proposals were flowing again by 14:21 UTC, and the incident closed at 19:15 UTC. Block production and deposits were not part of it.

The onchain record shows a much longer gap than the status timeline suggests. On the Mainnet DisputeGameFactoryProxy (0x43edB88C4B80fDD2AdFF2412A7BebF9dF42cB40e), game 23770 was created on October 8 at 14:46 UTC, and the next one, game 23771, not until October 9 at 14:08 UTC. Before that, a new game (type 621) landed about every 20 minutes. So no proposals went up for roughly 23 hours, most of it before the incident was posted. After the restart the proposer moved slowly at first, then filed a burst of more than 80 games between about 18:28 and 19:37 UTC to catch up, and returned to its usual 20-minute pace.

A withdrawal can only be proven against a proposal that covers its L2 block. Withdrawals started during the gap therefore waited up to about a day longer than usual before the proof step was possible. Once proven, the normal finalization delay still applies on top.

2026-10-08 — mainnet.base.org loses debug, trace, and txpool (completed)

Section titled “2026-10-08 — mainnet.base.org loses debug, trace, and txpool (completed)”

From Thursday, October 8th at 12:00 UTC, the free public endpoint https://mainnet.base.org stops answering the debug, trace, and txpool namespaces. Reads that remain get a tighter rate limit. The endpoint stays free and best-effort for basic reads. The notice went up on October 1 and gives a window that ends October 9 at 12:00 UTC. Any app that calls those namespaces on the public host, or needs more throughput than the new limit allows, must move to a dedicated node provider.

The status page closed the work on October 8 at 19:42 UTC, well inside the window. A probe of the public host on October 9 confirmed the cut: txpool_status came back as an unsupported method (-32604), a debug_ call was refused by the request filter (-32611), and eth_blockNumber still answered normally.

2026-10-05 — V1 node snapshots retired (completed)

Section titled “2026-10-05 — V1 node snapshots retired (completed)”

From Monday, October 5th at 12:00 UTC, Base stopped publishing V1 node database snapshots and stopped serving the ones already out there. The notice went up on September 29 with a 24-hour window ending October 6 at 12:00 UTC. The status page marked the work complete on October 6 at 14:00 UTC, two hours past that window. Operators who still restore from V1 need to move to the V2 snapshots at chain.base.org/snapshots; see Snapshots for the restore steps.

2026-09-30 — Mainnet Cobalt upgrade (completed)

Section titled “2026-09-30 — Mainnet Cobalt upgrade (completed)”

The window opened on schedule at 18:00 UTC and closed as complete at 20:00 UTC. No incident was raised against it.

Base Mainnet was scheduled to activate the Cobalt hardfork on Wednesday, September 30th at 18:00 UTC (Unix timestamp 1790791200), with a maintenance window running until 20:00 UTC. The notice went up on September 23 at 23:00 UTC, a few hours after the Sepolia window closed. Mainnet operators must run v1.4.2 of github.com/base/base or a later release. That is a higher floor than the compiled-in timestamp alone implies: v1.4.1 already carries the Mainnet value, but v1.4.2 adds a backport (#5260) that registers the validity transaction RPC ahead of Cobalt and switches it on from the live upgrade schedule. Details are in the Cobalt Upgrade Overview.

2026-09-23 — Sepolia Cobalt upgrade (completed)

Section titled “2026-09-23 — Sepolia Cobalt upgrade (completed)”

The maintenance window opened on time at 18:00 UTC and was marked complete at 20:00 UTC, with no incident reported against it.

Base Sepolia is scheduled to activate the Cobalt hardfork on Wednesday, September 23rd at 18:00 UTC (Unix timestamp 1790186400), with a maintenance window held open until 20:00 UTC. Operators of Sepolia nodes must be running the v1.4.0 release of github.com/base/base or later; earlier builds have no Cobalt timestamp compiled in and will not follow the fork. That floor applies to Sepolia only. The Mainnet activation timestamp was not added to the source until 2026-09-21, after v1.4.0 was tagged, so Mainnet operators need a later build for their own September 30 window. The notice also restates where node software now comes from: github.com/base/base publishes the public node that used to ship from base/node. Scope and migration notes are in the Cobalt Upgrade Overview.

2026-07-28 — Mainnet safe head fell behind

Section titled “2026-07-28 — Mainnet safe head fell behind”

At 13:10 UTC on Tuesday, July 28th, the safe head on Base Mainnet was reported as lagging. Unsafe block production was unaffected — the delay was confined to the batching of L2 data down to Ethereum L1, so chain progress at the tip continued as normal. The safe head was advancing again by 15:13 UTC, when the incident was closed.

2026-07-21 — Mainnet Flashblocks websocket capacity reduced

Section titled “2026-07-21 — Mainnet Flashblocks websocket capacity reduced”

On Tuesday, July 21st, the Flashblocks websocket stream on Base Mainnet ran at reduced capacity for roughly fifty minutes, spanning 19:50 to 20:42 UTC. Subscribers were likely to see messages arrive late over that window, and fresh connection attempts could come back rate limited. The event was marked resolved once stream capacity recovered.

Beginning at 16:03 UTC on Thursday, June 25th, Base Mainnet block production turned unhealthy. The team traced it to a consensus fault: an invalid block had been sequenced, which kept new blocks from being built past block 47806542. Sequencing of fresh blocks was restored by around 17:51 UTC, though ecosystem node operators had to restart their Base nodes to resume syncing. Healthy block building was confirmed shortly after, and the Beryl hardfork still activated on schedule at 18:00 UTC. By 19:22 UTC the network was stable with recovery verified across the ecosystem; any nodes still stuck at block 47806542 recover on restart. The root cause was identified and a fix put under verification, with a full post-mortem and root-cause analysis promised to the ecosystem.

2026-06-25 — Mainnet Beryl upgrade (scheduled)

Section titled “2026-06-25 — Mainnet Beryl upgrade (scheduled)”

Base Mainnet is scheduled to activate the Beryl hardfork on Thursday, June 25th at 18:00 UTC (Unix timestamp 1782410400). Operators of Mainnet nodes must move to the 1.1.1 release or later of github.com/base/base, with matching preconfigured binaries published as the v1.1.1 release of github.com/base/node. Migration steps are documented in the Beryl Upgrade Overview.

2026-06-18 — Sepolia Beryl upgrade (scheduled)

Section titled “2026-06-18 — Sepolia Beryl upgrade (scheduled)”

Base Sepolia is scheduled to activate the Beryl hardfork on Thursday, June 18th at 18:00 UTC (1781805600). Operators of Sepolia nodes need to move to the v1.1.0 release or later of github.com/base/base, with matching preconfigured builds shipped as the v1.1.0 release of github.com/base/node. The migration details live in the Beryl Upgrade Overview.

2026-06-12 — Mainnet p2p peering instability

Section titled “2026-06-12 — Mainnet p2p peering instability”

On Friday, June 12th at 21:28 UTC, the team began investigating peering problems on Base Mainnet where newly started nodes were having trouble finding peers. As a temporary measure, affected operators were pointed at a short list of --trusted-peers enode entries to add to their Reth node and restart while a fix was developed.

2026-06-02 — Mainnet Flashblocks broadcasting degraded

Section titled “2026-06-02 — Mainnet Flashblocks broadcasting degraded”

On Tuesday, June 2nd at 22:32 UTC, the team began investigating periodic instability in Flashblocks broadcasting on Base Mainnet. Pre-confirmation delivery was affected, but transaction inclusion in sealed blocks was reported as unaffected throughout.

2026-05-29 — Mainnet withdrawal delay (TEE enclave)

Section titled “2026-05-29 — Mainnet withdrawal delay (TEE enclave)”

On Friday, May 29th at 15:55 UTC, Base Mainnet withdrawals began running late after a TEE enclave fault stopped output proposals from being posted. The issue was identified and a fix was reported in progress; withdrawals resume once proposals catch back up.

2026-05-28 — Mainnet Azul upgrade (scheduled)

Section titled “2026-05-28 — Mainnet Azul upgrade (scheduled)”

Base Mainnet activates the Azul hardfork on Thursday, May 28th at 18:00 UTC. Node operators must run version 0.9.0 or later of github.com/base/base, with corresponding preconfigured binaries published as the v0.16.0 release of github.com/base/node. From this upgrade onward, base-consensus and base-reth-node are the only supported clients — op-node and op-geth will not follow the new chain. Pending withdrawals will be invalidated by the upgrade; users with in-flight withdrawals will need to submit a second proof transaction afterward to complete them. Migration steps are documented in Base v1 upgrade.