Network
Solana
SolanaSOL · 420 ms block time · 3 providers, 5 endpoints
Who is producing blocks
leader schedule · epoch 0
Solana fixes its leader schedule for a whole epoch before the epoch begins and publishes it, so who produces each of the next 432,000 slots is a known fact rather than a forecast. No other chain measured here publishes one. The map beside it marks where the validator taking its turn was last observed on the network.
Block production
epoch 0 · 0.0% through
slot 0 of 0 in this epoch · absolute 0
Leading now
The schedule for this epoch has not been read yet.
Last observed
—
projected since
Next up
- Waiting for the next schedule window…
The Solana chain position has not been sampled yet. Nothing is projected from nothing.
No Solana network locations have been resolved yet. The map is built from addresses observed in the cluster’s own gossip table and geolocated afterwards; until that has run, nothing is shown rather than a guess.
Solana slots advance roughly every 400ms, with the observed rate slightly slower because of skipped slots. Commitment levels (processed, confirmed, finalized) mean two healthy providers can legitimately report different heads, so every head is observed at a fixed commitment and compared against the cohort rather than against any single provider.
Provider ranking
30d window · generated 2026-08-24 15:46:13 UTC
No measurements in this window.
Either no probe has reported for this chain yet, or the window is shorter than the collection interval. Try a longer window.
The score weights availability at 40%, latency at 30%, correctness at 20% and head freshness at 10%. Correctness also acts as a ceiling: a provider that answers quickly and wrongly cannot be rated healthy on speed alone. Full methodology
Head freshness
30d window · generated 2026-08-24 15:46:13 UTC · cohort of 0
How far behind the chain each provider's data is. Latency cannot answer this: an endpoint can reply in 8 ms with a head from four minutes ago, and every speed measurement will still rate it excellent.
No head comparison available for Solana in this window.
Freshness requires at least two providers measured on the same chain within one window. A provider compared against itself is not a comparison, so nothing is published rather than a figure that would mean nothing.
From each region
The same Solana measurements, grouped by the vantage point they were taken from. A provider that answers in 40 ms from one region can take 220 ms from another, and the ranking above is an average across whichever regions are reporting.
Nothing was measured from any region in this window.
Percentiles are over successful responses only. A request that timed out is not a latency sample; it is counted against availability instead.