Monday, November 16, 2026

No, Polkadot is producing blocks

Its newest block, number 33,895,798, was made 7 s before our check at 02:16 UTC, by the chain's own clock. It normally makes one every 6 s.

Read from the chain 56 s ago

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.

6 snormal time between blocks
6 saverage over the last hour
24 s behindfinalityGRANDPA, ~12–18 s
Nonehalts on record
100%uptime we measured, last 3 days
?on one client, one dominant client

Halts over time

Every halt and finality stall on record for Polkadot 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 Polkadot 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.

0 ms6 s12 s12 Nov 21:00 UTC: 6 s per block12 Nov 22:00 UTC: 6 s per block12 Nov 23:00 UTC: 6 s per blockFri 1313 Nov 00:00 UTC: 6 s per block13 Nov 01:00 UTC: 6 s per block13 Nov 02:00 UTC: 6 s per block13 Nov 03:00 UTC: 6 s per block13 Nov 04:00 UTC: 6 s per block13 Nov 05:00 UTC: 6 s per block13 Nov 06:00 UTC: 6 s per block13 Nov 07:00 UTC: 6 s per block13 Nov 08:00 UTC: 6.1 s per block13 Nov 09:00 UTC: 6 s per block13 Nov 10:00 UTC: 6 s per block13 Nov 11:00 UTC: 6 s per block13 Nov 12:00 UTC: 6 s per block13 Nov 13:00 UTC: 6 s per block13 Nov 14:00 UTC: 6 s per block13 Nov 15:00 UTC: 6 s per block13 Nov 16:00 UTC: 6 s per block13 Nov 17:00 UTC: 6 s per block13 Nov 18:00 UTC: 6 s per block13 Nov 19:00 UTC: 6 s per block13 Nov 20:00 UTC: 6 s per block13 Nov 21:00 UTC: 6.1 s per block13 Nov 22:00 UTC: 6 s per block13 Nov 23:00 UTC: 6 s per blockSat 1414 Nov 00:00 UTC: 6 s per block14 Nov 01:00 UTC: 6 s per block14 Nov 02:00 UTC: 6 s per block14 Nov 03:00 UTC: 6.1 s per block14 Nov 04:00 UTC: 6 s per block14 Nov 05:00 UTC: 6 s per block14 Nov 06:00 UTC: 6 s per block14 Nov 07:00 UTC: 6 s per block14 Nov 08:00 UTC: 6 s per block14 Nov 09:00 UTC: 6 s per block14 Nov 10:00 UTC: 6 s per block14 Nov 11:00 UTC: 6 s per block14 Nov 12:00 UTC: 6 s per block14 Nov 13:00 UTC: 6 s per block14 Nov 14:00 UTC: 6 s per block14 Nov 15:00 UTC: 6.1 s per block14 Nov 16:00 UTC: 6 s per block14 Nov 17:00 UTC: 6 s per block14 Nov 18:00 UTC: 6 s per block14 Nov 19:00 UTC: 6 s per block14 Nov 20:00 UTC: 6 s per block14 Nov 21:00 UTC: 6 s per block14 Nov 22:00 UTC: 6 s per block14 Nov 23:00 UTC: 6 s per blockSun 1515 Nov 00:00 UTC: 6 s per block15 Nov 01:00 UTC: 6 s per block15 Nov 02:00 UTC: 6 s per block15 Nov 03:00 UTC: 6 s per block15 Nov 04:00 UTC: 6 s per block15 Nov 05:00 UTC: 6 s per block15 Nov 06:00 UTC: 6 s per block15 Nov 07:00 UTC: 6 s per block15 Nov 08:00 UTC: 6 s per block15 Nov 09:00 UTC: 6 s per block15 Nov 10:00 UTC: 6 s per block15 Nov 11:00 UTC: 6 s per block15 Nov 12:00 UTC: 6 s per block15 Nov 13:00 UTC: 6 s per block15 Nov 14:00 UTC: 6 s per block15 Nov 15:00 UTC: 6 s per block15 Nov 16:00 UTC: 6 s per block15 Nov 17:00 UTC: 6 s per block15 Nov 18:00 UTC: 6 s per block15 Nov 19:00 UTC: 6 s per block15 Nov 20:00 UTC: 6 s per block15 Nov 21:00 UTC: 6 s per block15 Nov 22:00 UTC: 6 s per block15 Nov 23:00 UTC: 6 s per blockMon 1616 Nov 00:00 UTC: 6 s per block16 Nov 01:00 UTC: 6 s per block16 Nov 02:00 UTC: 6 s per blocknormal 6 s

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.

DateTypeDurationWhat happenedSources
17 Sep 2024, 07:58 UTCDegraded≈14 minThe runtime 1.3.0 upgrade migrated HostConfiguration at the end of the block, so a runtime API read corrupted values and the candidate-backing subsystem stalled; relay finality lagged about 70 blocks and parachains nearly stopped.
Note on timesRelay finality caught up around 08:12 UTC; parachain collators needed manual restarts from about 08:30 UTC. The relay chain did not fully halt.
forum.polkadot.network

Before 2024: No Polkadot relay-chain block-production halt found. In range there is the Sep 17 2024 finality lag (degraded, in incidents). Kusama (not Polkadot) had finality/block stalls in 2024-2025, and Polkadot parachains, People Chain and Asset Hub had stalls in 2026 with the relay chain unaffected. Source

Client software

Polkadot SDK node (Parity) One dominant client

Most validators run Parity's node built from the Polkadot SDK. Independent clients exist (KAGOME, Gossamer), but validators do not publish which one they run, so their share is unknown.

ChainReport review of official repositories and docs, 12 Nov 2026. Compare all chains

Compare

Embed this status

Show the live Polkadot status in your docs, dashboard or README.

Is Polkadot down? Live status by ChainReport

The badge updates about once a minute and links back to this page. Feed for Polkadot incidents: Atom.

Links

We read Polkadot from two places: first source PublicNode and second source Parity public RPC.

Other chains

Also on the Network Desk for Polkadot

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; Parity 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.

Scroll to Top
Chain Report
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.