Providers

BNB ChainExcellent

Official BNB Smart Chain data seed nodes operated by the BNB Chain project.

public · rank 3 of 12

Website (opens in a new tab)Documentation (opens in a new tab)

Measured performance

30d window · 30.0 days observed · 1 chain

Composite score

95.7

Rank 3 of 12

2,332,963 samples

Availability

99.97%

Rate limits and unsupported methods excluded

Latency p95

29.5ms

p50 18.4 · p99 50.1

Correctness

100.00%

2,309,376 responses judged

22795 of 2332937 requests were rate limited; excluded from availability

12 providers scored against each other.

Score breakdown

How the composite score is composed
Component	Weight	Measured	Score	How it is measured
Availability	40%	99.97 %	100.0	Share of requests that succeeded, excluding rate limits and unsupported methods.
Latency	30%	29.54 ms	100.0	Scored on p95 relative to the cohort, log-scaled so a 10x difference is not a 10x penalty.
Correctness	20%	100.00 %	100.0	Share of responses that were valid. Also caps the overall score, so speed cannot compensate for wrong answers.
Head freshness	10%	4.54 blocks behind	56.7	Distance behind the cohort head, measured against the highest plausible head across providers.

Outcome breakdown

Failures are classified rather than collapsed into one count. Our own failures are shown for transparency but are never counted against the provider.

Request outcomes and how each is treated
Outcome	Count	Share	Treatment
Successful	2,309,347	98.99%	—
Provider failure	22,824	0.98%	Counted against provider
Network failure	766	0.03%	Counted against provider
Rate limited	22,795	0.98%	Excluded from availability
Unsupported method	0	0.00%	Capability fact, not a failure
Agent error	0	0.00%	Ours, never the provider
Measurement error	26	0.00%	Ours, never the provider

What it says it permits

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.

What it promises about staying up

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

States a limitation of the public endpoint
applies to the public data seed endpoints
“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

Reliability record

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

Departures from normal · last 30 days

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.

Persistent conditions

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.

Throttledeth_getLogson BSCnever answered100% refused
Throttledeth_getLogson BSCnever answered100% refused
Throttledeth_getLogson BSCnever answered100% refused
Throttledeth_getLogson BSCnever answered100% refused

From each region

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.

BNB Chain broken out by region
Region	Median	p95	p99	Success	Rate limited	Samples
Virginia	4.4 ms	7.3 ms	19.1 ms	99.0%	5,724	583,675
Frankfurt	23.1 ms	27.3 ms	41.5 ms	99.0%	5,688	583,174
Coventry	17.3 ms	24.4 ms	48.3 ms	99.0%	5,695	583,251
Amsterdam	22.6 ms	37.1 ms	87.0 ms	99.0%	5,688	582,863

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

Endpoints under measurement

Endpoints measured for this provider
Chain	Transport	URL	Credentials	Status
BSC	http_jsonrpc	https://bsc-dataseed1.bnbchain.org	keyless
BSC	http_jsonrpc	https://bsc-dataseed.bnbchain.org	keyless

Embed this

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

score

The composite score, coloured by band.

Markdown

[![BNB Chain on RPCNode.IO](https://rpcnode.io/badge/provider/bnbchain.svg?chain=bsc)](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>