No, Linea is producing blocks
Its newest block, number 32,619,331, was made 8 s before our check at 02:16 UTC, by the chain's own clock. It normally makes one every 9.2 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 Linea 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 Linea 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 |
|---|---|---|---|---|
| 5 Oct 2026, 08:11 UTC | Finality stalled | ≈3 days | A prover/finalization issue delayed L1 finalization of Mainnet, while blocks kept being produced.Note on timesTimes are status-page post times. Proofs were generating normally from Oct 6 15:00 UTC, but finalization stayed delayed until the fix on Oct 8. Smaller L2->L1 finalization partial outages (Mar 23-26, May 23-24 and Jun 13-14, 2026) are not listed separately. | linea.statuspage.io |
| 8 Aug 2026 | Halt | not reported | A full outage of Mainnet block production stopped network progression and finality until the sequencer was restarted.Note on timesThe official status page gives no start time. Block production was already restored by the 11:44 UTC 'monitoring' update, and the incident was closed Aug 10 03:56 UTC. Duration unknown. | linea.statuspage.io |
| 28 Oct 2025, 10:38 UTC | Halt | ≈1.6 h | Mainnet block production stalled at block 24,992,514; no cause was disclosed.Note on timesTimes come from QuickNode's status page (first 'investigating' post to 'resolved'), so the real start may be earlier. No Linea post-mortem was found. | status.quicknode.com |
| 10 Sep 2025, 05:25 UTC | Halt | ≈67 min | The mainnet sequencer stopped producing blocks after block 23,145,386 on the day of the LINEA token launch; Linea said it found and fixed the issue but did not disclose a root cause.Note on timesTimes converted from 1:25-2:32 a.m. ET (EDT). Other coverage cites a 46-minute gap between blocks 23,145,386 and 23,145,387. An aggregator also lists a ~11h incident on Sep 11 at block 23,202,037, which could not be verified. | theblock.co |
| 2 Jun 2024 | Halt | not reported | Linea deliberately paused its sequencer between blocks 5081800 and 5081801 to stop the Velocore DEX exploiter from bridging funds out.Note on timesIntentional halt, not a failure. Sources give no UTC start or resume time. The block explorers (lineascan) refused automated fetches, so the block timestamps could not be checked. Date approximate (exploit Jun 2, 2024; coverage Jun 3). | theblock.co |
Before 2024: Linea mainnet launched in July 2023; no halt found before 2024. Source
Client software
Single sequencer (Linea) Single implementation
Blocks come from one sequencer run by Consensys. If that sequencer or its software fails, block production stops for everyone, as the historical record below shows. Users can still force transactions through Ethereum, slowly.
ChainReport review of official repositories and docs, 12 Nov 2026. Compare all chains
Compare
Embed this status
Show the live Linea status in your docs, dashboard or README.
The badge updates about once a minute and links back to this page. Feed for Linea incidents: Atom.
Links
We read Linea from two places: first source PublicNode and second source Linea public RPC.
Other chains
Also on the Network Desk for Linea
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; Linea public RPC; 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.