Monday, November 16, 2026

Cosmos Hub vs Polkadot

Which of the two halts less? Live status, outage record and software risk side by side.

Updated 60 s ago
Since 2024, Polkadot has been down less than Cosmos Hub: 84 s of weighted downtime against 29 h. Halts count in full; finality stalls count a quarter and degradations a tenth of their duration, as in the league.
vs
Cosmos HubPolkadot
Right nowProducing blocks
newest block 14 s old
Producing blocks
newest block 7 s old
League position#28 of 28#12 of 28
Since last halt53 daysNone on record
Halts since 202420
Time halted since 202429 h—
Longest halt25 h—
Other incidents01
Uptime we measured100% (3 days)100% (3 days)
Block pace5.7 s typical, 5.7 s last hour6 s typical, 6 s last hour
FinalityInstant (CometBFT)GRANDPA, ~12–18 s
Client softwareGaia (CometBFT)
Single implementation
Polkadot SDK node (Parity)
One dominant client

Incidents on record

Popular comparisons

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.

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.