Monday, November 16, 2026

No, Solana is producing slots

Its newest slot, number 469,957,938, was made 1 s before our check at 02:07 UTC, by the chain's own clock. It normally makes one every 215 ms.

Read from the chain just now

Each mark is a minute of slots; 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.

215 msnormal time between slots
216 msaverage over the last hour
Not measuredfinalityTower BFT, seconds (not measurable on free RPC)
1,013days since the last halt
100%uptime we measured, last 3 days
82%on one client, over two-thirds

Halts over time

Every halt and finality stall on record for Solana 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 Solana ourselves since 12 Nov 2026; anything earlier is from the public record.

Block production, hour by hour

Average time between slots 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 ms215 ms430 ms12 Nov 21:00 UTC: 216 ms per slot12 Nov 22:00 UTC: 215 ms per slot12 Nov 23:00 UTC: 216 ms per slotFri 1313 Nov 00:00 UTC: 216 ms per slot13 Nov 01:00 UTC: 216 ms per slot13 Nov 02:00 UTC: 216 ms per slot13 Nov 03:00 UTC: 216 ms per slot13 Nov 04:00 UTC: 215 ms per slot13 Nov 05:00 UTC: 215 ms per slot13 Nov 06:00 UTC: 215 ms per slot13 Nov 07:00 UTC: 216 ms per slot13 Nov 08:00 UTC: 215 ms per slot13 Nov 09:00 UTC: 215 ms per slot13 Nov 10:00 UTC: 215 ms per slot13 Nov 11:00 UTC: 215 ms per slot13 Nov 12:00 UTC: 216 ms per slot13 Nov 13:00 UTC: 216 ms per slot13 Nov 14:00 UTC: 216 ms per slot13 Nov 15:00 UTC: 216 ms per slot13 Nov 16:00 UTC: 216 ms per slot13 Nov 17:00 UTC: 215 ms per slot13 Nov 18:00 UTC: 215 ms per slot13 Nov 19:00 UTC: 216 ms per slot13 Nov 20:00 UTC: 215 ms per slot13 Nov 21:00 UTC: 216 ms per slot13 Nov 22:00 UTC: 215 ms per slot13 Nov 23:00 UTC: 215 ms per slotSat 1414 Nov 00:00 UTC: 215 ms per slot14 Nov 01:00 UTC: 215 ms per slot14 Nov 02:00 UTC: 215 ms per slot14 Nov 03:00 UTC: 215 ms per slot14 Nov 04:00 UTC: 215 ms per slot14 Nov 05:00 UTC: 215 ms per slot14 Nov 06:00 UTC: 215 ms per slot14 Nov 07:00 UTC: 215 ms per slot14 Nov 08:00 UTC: 215 ms per slot14 Nov 09:00 UTC: 215 ms per slot14 Nov 10:00 UTC: 214 ms per slot14 Nov 11:00 UTC: 215 ms per slot14 Nov 12:00 UTC: 215 ms per slot14 Nov 13:00 UTC: 214 ms per slot14 Nov 14:00 UTC: 215 ms per slot14 Nov 15:00 UTC: 215 ms per slot14 Nov 16:00 UTC: 215 ms per slot14 Nov 17:00 UTC: 215 ms per slot14 Nov 18:00 UTC: 216 ms per slot14 Nov 19:00 UTC: 215 ms per slot14 Nov 20:00 UTC: 215 ms per slot14 Nov 21:00 UTC: 216 ms per slot14 Nov 22:00 UTC: 215 ms per slot14 Nov 23:00 UTC: 216 ms per slotSun 1515 Nov 00:00 UTC: 215 ms per slot15 Nov 01:00 UTC: 215 ms per slot15 Nov 02:00 UTC: 215 ms per slot15 Nov 03:00 UTC: 215 ms per slot15 Nov 04:00 UTC: 215 ms per slot15 Nov 05:00 UTC: 214 ms per slot15 Nov 06:00 UTC: 215 ms per slot15 Nov 07:00 UTC: 215 ms per slot15 Nov 08:00 UTC: 215 ms per slot15 Nov 09:00 UTC: 215 ms per slot15 Nov 10:00 UTC: 215 ms per slot15 Nov 11:00 UTC: 215 ms per slot15 Nov 12:00 UTC: 215 ms per slot15 Nov 13:00 UTC: 214 ms per slot15 Nov 14:00 UTC: 215 ms per slot15 Nov 15:00 UTC: 215 ms per slot15 Nov 16:00 UTC: 215 ms per slot15 Nov 17:00 UTC: 215 ms per slot15 Nov 18:00 UTC: 215 ms per slot15 Nov 19:00 UTC: 215 ms per slot15 Nov 20:00 UTC: 215 ms per slot15 Nov 21:00 UTC: 214 ms per slot15 Nov 22:00 UTC: 215 ms per slot15 Nov 23:00 UTC: 216 ms per slotMon 1616 Nov 00:00 UTC: 215 ms per slot16 Nov 01:00 UTC: 216 ms per slot16 Nov 02:00 UTC: 214 ms per slotnormal 215 ms

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
6 Feb 2024, 09:53 UTCHalt≈5.1 hA bug in the validator's JIT-compilation cache (Agave v1.17) left nearly all validators stuck in a recompile loop, so voting and consensus stopped until a patched v1.17.20 restart.
Note on timesTimes from the Anza postmortem as quoted in search results (postmortem page returned 429 when opened); Cointelegraph (opened) gives 10:22 UTC as the start.
solana.com
cointelegraph.com

Client software

Agave codebase Over two-thirds

By stake

Agave and Agave-based (Jito, BAM, Harmonic, Rakurai) 81.5%Firedancer family (incl. Frankendancer, Harmonic, FireBAM) 18.1%Other / unknown 0.4%

Client labels reported

AgaveBam 38.5%HarmonicAgave 21.4%JitoLabs 19.4%HarmonicFiredancer 11.0%Firedancer 5.1%FireBAM 2.0%Rakurai 1.2%

Jito, BAM, Harmonic and Rakurai builds are modified versions of Agave and share its code, so a bug in Agave code can hit all of them at once. Frankendancer, counted under Firedancer, still uses parts of Agave too, so the real Agave share is higher.

Stakewiz validator list, share of active stake, 15 Nov 2026. Compare all chains

Compare

Embed this status

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

Is Solana down? Live status by ChainReport

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

Links

We read Solana from two places: first source PublicNode.

Other chains

Also on the Network Desk for Solana

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.

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.