No, Avalanche C-Chain is producing blocks
Its newest block, number 100,439,430, was made 8 s before our check at 02:16 UTC, by the chain's own clock. It normally makes one every 945 ms.
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 Avalanche C-Chain 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 Avalanche C-Chain 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 |
|---|---|---|---|---|
| 23 Feb 2024, 11:13 UTC | Halt | ≈5.4 h | A gossip/mempool-management bug, triggered by an inscription wave, filled validators' bandwidth with useless gossip so consensus pull queries stalled; fixed in AvalancheGo v1.11.1.Note on timesStart from Forklog (11:13 UTC); finalization resumed 11:36 ET per The Block. The Block calls it ~6 hours; others say 2-4 hours. | theblock.co forklog.com |
Client software
AvalancheGo Single implementation
All validators run AvalancheGo, maintained by Ava Labs.
ChainReport review of official repositories and docs, 12 Nov 2026. Compare all chains
Compare
Embed this status
Show the live Avalanche C-Chain status in your docs, dashboard or README.
The badge updates about once a minute and links back to this page. Feed for Avalanche C-Chain incidents: Atom.
Links
We read Avalanche C-Chain from two places: first source PublicNode and second source Avalanche public API.
Other chains
Also on the Network Desk for Avalanche
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; Avalanche public API; 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.