No, Starknet is producing blocks
Its newest block, number 18,033,749, was made 7 s before our check at 02:16 UTC, by the chain's own clock. It normally makes one every 1.7 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 Starknet 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 Starknet 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 |
|---|---|---|---|---|
| 18 Mar 2026 | Halt | ≈11 min | Mainnet was down for 11 minutes during planned maintenance for the 0.14.1 committer upgrade.Note on timesPlanned maintenance, not an unplanned failure. Only the 07:30 UTC entry time is known. Other planned upgrade windows (Jul 8, 2026, ~10 min; Oct 6, 2026, ~5-10 min) are excluded. | status.starknet.io |
| 5 Jan 2026, 09:42 UTC | Halt | ≈4.6 h | A blockifier bug restored state incorrectly when a nested call panicked and was caught, so sequencing was paused and the chain was reorged to drop the bad execution.Note on timesActivity from 09:24-09:42 UTC (18 min) was also reverted, so total impact was 09:24-14:17 (~293 min). The status page lists 09:53-14:02 with a revert to block 5187263. Press reported 2-4h. | starknet.io status.starknet.io |
| 9 Oct 2025 | Degraded | not reported | Aerospike database hotspots from preconfirmed-block fetches stalled the committer, and a transaction execution-time misconfiguration caused repeated retry loops, producing a series of short stalls.Note on timesSeries of downtimes, mostly a few minutes each, with three lasting 10-20 minutes. The official forum post gives no per-event timestamps. | community.starknet.io |
| 2 Sep 2025, 02:20 UTC | Halt | ≈11 h | After the v0.14.0 (Grinta) upgrade, Ethereum node failures gave the three sequencers different views of L1, a manual intervention produced conflicting blocks, and a blockifier bug in reprocessing reverted L1-to-L2 messages forced two reorgs.Note on timesOfficial report: three halts within the window, 02:20-03:57, 04:37-07:42 and 10:43-13:41 UTC (~460 min actually halted, ~9h degraded overall). Reorg 1 rolled back to block 1,960,612 and reorg 2 rolled back from 1,962,681, reverting ~1.5h of transactions. Early Cointelegraph coverage said 2h44m (02:23-04:36), which was only the first phase. | starknet.io cointelegraph.com |
| 4 Apr 2024 | Degraded | ≈4 h | A rounding-error bug forced a block reorganization, leaving a roughly four-hour gap in blocks and briefly rejecting or reverting some transactions.Note on timesApproximate. Starkscan shows a ~4h gap between blocks 630028 and 630029 on Apr 4 (the article's lead says Apr 5). Starknet's status page showed no outage, and Starknet said block production continued, so whether this was a true halt is disputed. No UTC times given. | cointelegraph.com |
Before 2024: 15 Nov 2023. Block production stalled for about 50 minutes (a 40-minute gap, then a 10-minute gap) from 10:00 GMT, when a transaction influx overloaded the gateway's single deduplicator. Source
Client software
Single sequencer (Starknet) Single implementation
Blocks come from one sequencer run by StarkWare. 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 Starknet status in your docs, dashboard or README.
The badge updates about once a minute and links back to this page. Feed for Starknet incidents: Atom.
Links
We read Starknet from two places: first source PublicNode.
Other chains
Also on the Network Desk for Starknet
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; 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.