Composite score
95.6
Rank 1 of 12
16,421 samples
Providers
Official BNB Smart Chain data seed nodes operated by the BNB Chain project.
public · rank 1 of 12
Website (opens in a new tab)Documentation (opens in a new tab)
6h window · 6.0 hours observed · 1 chain
95.6
Rank 1 of 12
16,421 samples
99.99%
Rate limits and unsupported methods excluded
25.3ms
p50 18.3 · p99 42.9
99.99%
16,263 responses judged
158 of 16421 requests were rate limited; excluded from availability
12 providers scored against each other.
| Component | Weight | Measured | Score |
|---|---|---|---|
| Availability | 40% | 99.99 % | 100.0 |
| Latency | 30% | 25.26 ms | 100.0 |
| Correctness | 20% | 99.99 % | 100.0 |
| Head freshness | 10% | 4.61 blocks behind | 56.2 |
Failures are classified rather than collapsed into one count. Our own failures are shown for transparency but are never counted against the provider.
| Outcome | Count | Share |
|---|---|---|
| Successful | 16,261 | 99.03% |
| Provider failure | 160 | 0.97% |
| Network failure | 0 | 0.00% |
| Rate limited | 158 | 0.96% |
| Unsupported method | 0 | 0.00% |
| Agent error | 0 | 0.00% |
| Measurement error | 0 | 0.00% |
The only figures on this site that are not measurements. A limit is a claim the operator makes, so it is quoted with the page it came from and the day it was read — never inferred from a refused request, which would put a number against a company that never stated it.
Requestson BSC10,000 / 300s
per IP address
“The rate limit of BSC endpoint on Testnet and Mainnet is 10K/5min.”
Quoted, not measured. Read 2026-08-15 from docs.bnbchain.org— a provider can change this without telling anybody, so the date is part of the figure.
The status page judges every provider against an objective this site publishes. That is not an SLA, and a provider that misses it has not broken a promise — so what it actually promised, where it promised anything, belongs here in its own words. The objective
“eth_getLogs is disabled on below Mainnet endpoints — it is recommended to use third-party providers or WebSockets for frequent log queries.”
Quoted, not measured. Read 2026-08-15 from docs.bnbchain.org
An availability percentage has no shape. This is the shape: what departed from this provider’s own normal behaviour, and what its normal behaviour already is. How an incident is decided
None. Across the last 30 days, BNB Chain did not depart from its own usual behaviour on any measured call for long enough to count as an incident.
Calls that fail, or are refused, at about the same rate every day. These are not events — they are what this provider does — and none of them will be different tomorrow.
The same measurements, grouped by the vantage point they were taken from. Latency is a property of a network path, so a provider fast from one region is not necessarily fast from another — and the composite score above is an average across whichever regions are reporting.
Percentiles are over successful responses only. A request that timed out is not a latency sample; it is counted against availability instead.
A live badge for BNB Chain on BSC, free to use. It renders from the current measurement each time it loads, so it cannot be frozen at a good day — which is what makes it worth putting in a README. Every badge and parameter
The composite score, coloured by band.
Markdown
[](https://rpcnode.io/providers/bnbchain)HTML
<a href="https://rpcnode.io/providers/bnbchain"><img src="https://rpcnode.io/badge/provider/bnbchain.svg?chain=bsc" alt="BNB Chain on RPCNode.IO"></a>