Monday, November 16, 2026

No, Bitcoin is producing blocks

Its newest block, number 976,054, was made 6 min before our check at 02:16 UTC, by the chain's own clock. Proof-of-work blocks arrive at random, about every 10.5 min on average, so a wait of several times that is normal now and then.

Read from the chain just now

Each mark is one block. Hatched stretches are halts we confirmed. Point at the rail or use the arrow keys to read it.

10.5 minnormal time between blocks
5.1 minaverage over the last hour
Probabilisticfinality6 blocks ≈ 1 h
4,998days since the last halt
100%uptime we measured, last 3 days
90%on one client, over two-thirds

Halts over time

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

No halt or finality stall on record for Bitcoin since 1 January 2024.

We have measured Bitcoin 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 ms27.8 min55.6 min12 Nov 21:00 UTC: 3.1 min per block12 Nov 22:00 UTC: 10.3 min per block12 Nov 23:00 UTC: 17.3 min per blockFri 1313 Nov 00:00 UTC: 13.4 min per block13 Nov 01:00 UTC: 55.6 min per block13 Nov 02:00 UTC: 11.1 min per block13 Nov 03:00 UTC: 5.9 min per block13 Nov 04:00 UTC: 14.7 min per block13 Nov 05:00 UTC: 25.7 min per block13 Nov 06:00 UTC: 27.4 min per block13 Nov 07:00 UTC: 11.8 min per block13 Nov 08:00 UTC: 8 min per block13 Nov 09:00 UTC: 7.7 min per block13 Nov 10:00 UTC: 10.5 min per block13 Nov 11:00 UTC: 12.8 min per block13 Nov 12:00 UTC: 15.6 min per block13 Nov 13:00 UTC: 8.5 min per block13 Nov 14:00 UTC: 7.2 min per block13 Nov 15:00 UTC: 13.1 min per block13 Nov 16:00 UTC: 21.3 min per block13 Nov 17:00 UTC: 31.6 min per block13 Nov 18:00 UTC: 11.4 min per block13 Nov 19:00 UTC: 26.7 min per block13 Nov 20:00 UTC: 10.5 min per block13 Nov 21:00 UTC: 9.2 min per block13 Nov 22:00 UTC: 18.3 min per block13 Nov 23:00 UTC: 16.6 min per blockSat 1414 Nov 00:00 UTC: 14.5 min per block14 Nov 01:00 UTC: 32.9 min per block14 Nov 02:00 UTC: 13.6 min per block14 Nov 03:00 UTC: 9.7 min per block14 Nov 04:00 UTC: 26.8 min per block14 Nov 05:00 UTC: 8.1 min per block14 Nov 06:00 UTC: 17.2 min per block14 Nov 07:00 UTC: 4.8 min per block14 Nov 08:00 UTC: 8.3 min per block14 Nov 09:00 UTC: 6.9 min per block14 Nov 10:00 UTC: 21.6 min per block14 Nov 11:00 UTC: 10.7 min per block14 Nov 12:00 UTC: 11.3 min per block14 Nov 13:00 UTC: 6.8 min per block14 Nov 14:00 UTC: 8.8 min per block14 Nov 15:00 UTC: 11.6 min per block14 Nov 16:00 UTC: 16 min per block14 Nov 17:00 UTC: 9.9 min per block14 Nov 18:00 UTC: 13.4 min per block14 Nov 19:00 UTC: 8.6 min per block14 Nov 20:00 UTC: 7.4 min per block14 Nov 21:00 UTC: 8.1 min per block14 Nov 22:00 UTC: 10.9 min per block14 Nov 23:00 UTC: 12.1 min per blockSun 1515 Nov 00:00 UTC: 10.5 min per block15 Nov 01:00 UTC: 8.7 min per block15 Nov 02:00 UTC: 7.2 min per block15 Nov 03:00 UTC: 5.4 min per block15 Nov 04:00 UTC: 6.5 min per block15 Nov 05:00 UTC: 13.2 min per block15 Nov 06:00 UTC: 4.8 min per block15 Nov 07:00 UTC: 13.5 min per block15 Nov 08:00 UTC: 16 min per block15 Nov 09:00 UTC: 5.4 min per block15 Nov 10:00 UTC: 9.1 min per block15 Nov 11:00 UTC: 6.6 min per block15 Nov 12:00 UTC: 7.6 min per block15 Nov 13:00 UTC: 12.6 min per block15 Nov 14:00 UTC: 9.1 min per block15 Nov 15:00 UTC: 9.8 min per block15 Nov 16:00 UTC: 6.9 min per block15 Nov 17:00 UTC: 7.3 min per block15 Nov 18:00 UTC: 27.4 min per block15 Nov 19:00 UTC: 8.1 min per block15 Nov 20:00 UTC: 11.2 min per block15 Nov 21:00 UTC: 9.6 min per block15 Nov 22:00 UTC: 6.9 min per block15 Nov 23:00 UTC: 19.8 min per blockMon 1616 Nov 00:00 UTC: 6.2 min per block16 Nov 01:00 UTC: 6.1 min per block16 Nov 02:00 UTC: 4.5 min per blocknormal 10.5 min

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.

No halts, finality stalls or major degradations on record since January 2024.

Before 2024: 11 Mar 2013. Chain fork: v0.8 (LevelDB) nodes accepted a large block that pre-0.8 (BerkeleyDB lock limit) nodes rejected; pools downgraded to 0.7 to reorg it away. Before that, the Aug 2010 value-overflow incident. No halt in 2024-2026. Source

Client software

Bitcoin Core Over two-thirds

Reachable nodes

Bitcoin Core 89.9%Bitcoin Knots 9.8%Other 0.3%

Counts public nodes, not mining power. Knots is itself a patched version of Bitcoin Core, so they share most consensus code. Proof-of-work has no one-third / two-thirds voting threshold: a consensus bug would cause a split, not a halt.

Bitnodes crawl of 18,862 reachable nodes (user agents), 15 Nov 2026. Compare all chains

Compare

Embed this status

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

Is Bitcoin down? Live status by ChainReport

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

Links

We read Bitcoin from two places: first source mempool.space and second source Blockstream Esplora.

Other chains

Also on the Network Desk for Bitcoin

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: mempool.space; Blockstream Esplora; 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.