No, Ethereum is producing blocks
Its newest block, number 26,424,532, was made 8 s before our check at 02:16 UTC, by the chain's own clock. It normally makes one every 12 s.
Each mark is a minute of blocks; a shorter mark means fewer than normal. Hatched stretches are halts we confirmed. Point at the rail or use the arrow keys to read it.
Halts over time
Every halt and finality stall on record for Ethereum since 2024: from postmortems, status pages and news reports, plus the ones we measured ourselves. Point at a dot, or focus the rail and use the arrow keys; Enter opens the incident.
We have measured Ethereum ourselves since 12 Nov 2026; anything earlier is from the public record.
Block production, hour by hour
Average time between blocks for each hour over the last 7 days, or since we started measuring on 12 Nov 2026. The dashed line is the normal pace. Red hours contain a halt; empty hours are gaps in our sampling.
Halts we detected
None so far. We have been measuring since 12 Nov 2026.
The public record since 2024
From postmortems, status pages and news reports.
| Date | Type | Duration | What happened | Sources |
|---|---|---|---|---|
| 4 Dec 2025, 02:50 UTC | Degraded | ≈4.4 h | After Fusaka, a Prysm v7 bug (PR 15965) made Prysm nodes regenerate old states when they processed attestations from out-of-sync peers, exhausting resources; participation fell to ~75%, but finality was never lost.Note on timesTimes are converted from the impacted epoch range 411439-411480 (42 epochs) given on Prysm's postmortem page (prysm.offchainlabs.com/docs/misc/mainnet-postmortems/; quoted in search results, returned 404 when opened). Blocks were missed (18.5% missed slots) but the chain kept finalizing. | cointelegraph.com cointelegraph.com |
Before 2024: 12 May 2023. Last actual loss of finality: 3 epochs on May 11 and 9 epochs (~1 h) on May 12, 2023, from Prysm/Teku resource exhaustion on old attestations. Block production has never halted since the Merge. Dec 2025 Prysm/Fusaka was a near-miss (75% participation), not a finality loss. Source
Client software
Lighthouse (consensus) Over one-third
Execution clients
Nethermind 42.9%Geth 42.8%Besu 8.4%Reth 3.3%Erigon 2.7%Consensus clients
Lighthouse 47.1%Nimbus 19.1%Prysm 17.6%Teku 6.4%Unknown 3.2%Lodestar 2.7%Erigon 2.3%Grandine 1.6%Ethereum runs two pieces of software per validator. Both layers count: a bug in either can stop finality. Execution share covers about 59% of validators that reveal their client.
supermajority.info via clientdiversity.org; Miga Labs via clientdiversity.org, 15 Nov 2026. Compare all chains
Compare
Embed this status
Show the live Ethereum status in your docs, dashboard or README.
The badge updates about once a minute and links back to this page. Feed for Ethereum incidents: Atom.
Links
We read Ethereum from two places: first source PublicNode and second source dRPC.
Other chains
Also on the Network Desk for Ethereum
How this works and where the data comes from
What we measure. Every minute a server job asks each chain for its newest block and reads the timestamp the chain itself put in that block. "Last block" is now minus that timestamp, so it is accurate even if our own checks run late. "Last hour" is the average spacing between blocks over the past hour, also from block timestamps.
When we call a halt. A chain counts as halted when no new block has appeared for much longer than normal. The limit is set per chain: 2 minutes for most fast chains, 5–7 minutes for Scroll, ZKsync and Cardano, 14 minutes for Dogecoin, 30 minutes for Litecoin and 2 hours for Bitcoin, where long gaps happen by chance. Before declaring a halt we ask a second, independent data provider. If one provider is stale and the other is fresh, the chain is fine and we log the provider as lagging. For Solana, Sui and Cardano we have only one free source, so we wait for three stale checks in a row. Start time is the last block before the stop; end time is the first new block, within about a minute.
Finality. For Ethereum we read the last finalized checkpoint from the beacon chain (normally 2 epochs, about 13–19 minutes behind). For other EVM chains and Polkadot we read the newest "finalized" block from the node. On rollups (Base, Arbitrum, OP, ZKsync, Scroll), "finalized" means settled on Ethereum, which takes longer by design: hours on ZKsync. Free Solana endpoints do not report commitment levels reliably, so we do not show Solana finality.
Limits. We have been measuring since 12 Nov 2026; uptime figures cover only that period and say so. If our job misses minutes, a halt that started and ended entirely inside that gap would show up only as a slow hour in the chart. The historical record before our measurements comes from postmortems and news reports, with approximate times marked "≈". Hyperliquid is measured through HyperEVM, which stops whenever the HyperCore L1 stops.
Sources: PublicNode; dRPC; PublicNode Ethereum beacon API; Historical record: project postmortems, status pages, The Block, CoinDesk, Cointelegraph, Decrypt (linked per row)
Information only, not financial advice. Data comes from public sources and can be delayed or wrong; check the primary source before acting.