Network

BSC

BNB · chain id 56 · 450 ms block time · 5 providers, 8 endpoints

Just tell meWhich BNB Smart Chain provider leadsThe ranking below, read as an answer — with the figures behind it and what it refuses to claim.Before you payDo you need a dedicated node?What the free endpoints actually manage, and how often they refuse. Often the answer is no.

BNB Smart Chain uses Parlia with fast finality. Sub-second block times mean a single block of lag is normal and is not treated as staleness; the staleness threshold is derived from this block time rather than being a fixed number of blocks.

Provider ranking

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

1h window · generated 2026-10-27 11:17:47 UTC · cohort of 4

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.

Providers ranked by distance behind the cohort head
#	Provider	Mean blocks behind	≈ seconds	Worst blocks	Compared
1 (1st)	nodereal	1.67	0.75	27	579
2 (2nd)	blastapi	3.13	1.41	40	587
3 (3rd)	publicnode	3.43	1.54	40	600
4	bnbchain	3.87	1.74	43	1,189

Each observed head is compared against the cohort reference for its instant: the highest head any measured provider had reached, after discarding heads implausibly far above the cohort median and time-aligning samples taken moments apart. Lag is therefore relative to the fastest-updating provider in the set, not to an absolute truth. A cohort of fewer than two providers produces no freshness data at all.

From each region

The same BSC 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.

BSC broken out by region
Region	Median	p95	p99	Success	Rate limited	Samples
Amsterdam	20.1 ms	123 ms	136 ms	94.6%	78	2,091
Virginia	6.2 ms	23.0 ms	33.8 ms	93.8%	90	1,908
Coventry	83.6 ms	117 ms	336 ms	93.5%	94	1,906
Frankfurt	23.6 ms	111 ms	125 ms	92.6%	62	1,142

Percentiles are over successful responses only. A request that timed out is not a latency sample; it is counted against availability instead.