Network
BSC
BSCBNB · chain id 56 · 450 ms block time · 5 providers, 8 endpoints
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
1h window · 60 minutes observed · 4 vantage points · generated 2026-10-27 12:02:55 UTC
- Excellent / Good— Fast, available and correct all window
- Fair / Degraded— Measurable failures or slow tails
- Poor— Failing often enough to affect an application
- Insufficient data— Too few samples to score at all
- 4
- Provider
- Blast API
- Score
- 66.9
- Status
- Degraded
- Availability
- 100.0%
- p50 ms
- 104.4
- p95 ms
- 124.6
- Trend
- −6%
- Correct
- 100.0%
- Behind
- 2.92
- Samples
- 1,338
- 2 (2nd)
- Provider
- NodeReal
- Score
- 87.1
- Status
- Good
- Availability
- 99.6%
- p50 ms
- 23.6
- p95 ms
- 86.0
- Trend
- steady
- Correct
- 100.0%
- Behind
- 1.58
- Samples
- 1,387
- 3 (3rd)
- Provider
- BNB Chain
- Score
- 85.8
- Status
- Good
- Availability
- 100.0%
- p50 ms
- 22.1
- p95 ms
- 84.5
- Trend
- +14%
- Correct
- 100.0%
- Behind
- 4.52
- Samples
- 2,806
- 1 (1st)
- Provider
- PublicNode
- Score
- 96.1
- Status
- Excellent
- Availability
- 100.0%
- p50 ms
- 25.9
- p95 ms
- 69.3
- Trend
- +21%
- Correct
- 100.0%
- Behind
- 3.98
- Samples
- 1,409
- 5
- Provider
- 1RPConerpc
- Score
- 0.0
- Status
- Poor
- Availability
- 0.0%
- p50 ms
- 0.0
- p95 ms
- 0.0
- Trend
- not enough history
- Correct
- —
- Behind
- —
- Samples
- 322
- publicnode — 3% of requests targeted methods this provider offers only on a paid plan; excluded from availability
- bnbchain — 25 of 2806 requests were rate limited; excluded from availability
- blastapi — 2% of requests were rate limited (26 of 1338); excluded from availability
- onerpc — 99% of requests were rate limited (285 of 287); excluded from availability
5 providers scored against each other.
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
Latency over time
1h window · top 5 by score
95th percentile, computed over successful requests only. A request that timed out is not a latency sample; it is counted against availability instead. Gaps are gaps — periods with no collection are not bridged.
Head freshness
1h window · generated 2026-10-27 12:02:55 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.
| # | Provider | Mean blocks behind | ≈ seconds | Compared |
|---|---|---|---|---|
| 1 (1st) | nodereal | 1.58 | 0.71 | 602 |
| 2 (2nd) | blastapi | 2.92 | 1.32 | 569 |
| 3 (3rd) | publicnode | 3.98 | 1.79 | 628 |
| 4 | bnbchain | 4.52 | 2.03 | 1,238 |
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.
Virginia
Coventry
Frankfurt
AmsterdamPercentiles are over successful responses only. A request that timed out is not a latency sample; it is counted against availability instead.