Providers

NodeRealGood

BNB Chain infrastructure provider offering a shared public BSC endpoint.

commercial · rank 5 of 12

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

Measured performance

24h window · 2.2 hours observed · 2 chains

Composite score

84.2

Rank 5 of 12

6,793 samples

Availability

96.70%

Rate limits and unsupported methods excluded

Latency p95

97.7ms

p50 24.3 · p99 120.3

Correctness

99.98%

6,564 responses judged

12 providers scored against each other.

Score breakdown

How the composite score is composed
Component	Weight	Measured	Score	How it is measured
Availability	40%	96.70 %	96.7	Share of requests that succeeded, excluding rate limits and unsupported methods.
Latency	30%	97.73 ms	56.9	Scored on p95 relative to the cohort, log-scaled so a 10x difference is not a 10x penalty.
Correctness	20%	99.98 %	100.0	Share of responses that were valid. Also caps the overall score, so speed cannot compensate for wrong answers.
Head freshness	0%	not applicable	—	Not applicable across chains: blocks and slots are different units on different scales, so no cross-chain average is published. See the chain pages for this provider's head lag.

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	6,563	96.61%	—
Provider failure	1	0.01%	Counted against provider
Network failure	223	3.28%	Counted against provider
Rate limited	0	0.00%	Excluded from availability
Unsupported method	0	0.00%	Capability fact, not a failure
Agent error	0	0.00%	Ours, never the provider
Measurement error	6	0.09%	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.

NodeReal does not publish a numeric limit that could be found in its own documentation. Several public endpoints state only that a request may be refused — which is worth knowing before depending on one, and is why this says so rather than showing nothing.

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

NodeReal does not publish an availability commitment that could be found in its own documentation. That is the common case for a public endpoint and is worth knowing before depending on one: the availability figures on this site are measurements against a bar this platform set, not against anything NodeReal agreed to.

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

Degradedeth_blockNumberon BSC2026-08-24 22:1312m
Outageeth_getBlockByNumberon BSC2026-08-24 22:1311m
Degradedeth_blockNumberon BSC2026-08-24 21:503m
Outageeth_chainIdon BSC2026-08-24 21:334m
Degradedeth_blockNumberon BSC2026-08-24 21:324m
Outageeth_getBlockByNumberon BSC2026-08-24 21:324m

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.

Degradedeth_blockNumberon Ethereumsucceeds 80.3%
Degradedeth_getBlockByNumberon Ethereumsucceeds 79.5%
Degradedeth_chainIdon Ethereumsucceeds 79.8%
Outageeth_gasPriceon Ethereumsucceeds 81.3%
Outageeth_callon Ethereumsucceeds 76.2%
Outageeth_getBalanceon Ethereumsucceeds 82.5%
Outageeth_maxPriorityFeePerGason Ethereumsucceeds 79.2%
Outageeth_feeHistoryon Ethereumsucceeds 76.0%
Outageeth_estimateGason Ethereumsucceeds 76.0%

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.

NodeReal broken out by region
Region	Median	p95	p99	Success	Rate limited	Samples
Amsterdam	86.1 ms	94.0 ms	161 ms	99.9%	—	1,731
Frankfurt	34.5 ms	101 ms	123 ms	86.6%	—	1,710
Coventry	77.7 ms	90.0 ms	121 ms	100.0%	—	1,690
Virginia	5.7 ms	8.6 ms	21.7 ms	100.0%	—	1,662

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
BSC	http_jsonrpc	https://bsc-mainnet.nodereal.io/v1/redacted	keyless
BSC	ws_jsonrpc	wss://bsc-mainnet.nodereal.io/ws/v1/redacted	keyless
Ethereum	http_jsonrpc	https://eth-mainnet.nodereal.io/v1/redacted	keyless
Ethereum	ws_jsonrpc	wss://eth-mainnet.nodereal.io/ws/v1/redacted	keyless

Embed this

A live badge for NodeReal 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

[![NodeReal on RPCNode.IO](https://rpcnode.io/badge/provider/nodereal.svg?chain=bsc)](https://rpcnode.io/providers/nodereal)

HTML

<a href="https://rpcnode.io/providers/nodereal"><img src="https://rpcnode.io/badge/provider/nodereal.svg?chain=bsc" alt="NodeReal on RPCNode.IO"></a>