Providers

PublicNodeExcellent

Free public RPC endpoints operated by Allnodes across many chains, with no API key required.

public · rank 3 of 12

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

Measured performance

24h window · 24 hours observed · 3 chains

Composite score

93.0

Rank 3 of 12

120,693 samples

Availability

99.78%

Rate limits and unsupported methods excluded

Latency p95

53.3ms

p50 24.6 · p99 164.8

Correctness

99.78%

119,403 responses judged

0% of requests targeted methods this provider does not implement

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.78 %	99.8	Share of requests that succeeded, excluding rate limits and unsupported methods.
Latency	30%	53.31 ms	79.4	Scored on p95 relative to the cohort, log-scaled so a 10x difference is not a 10x penalty.
Correctness	20%	99.78 %	99.8	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	119,146	98.72%	—
Provider failure	1,541	1.28%	Counted against provider
Network failure	6	0.00%	Counted against provider
Rate limited	0	0.00%	Excluded from availability
Unsupported method	162	0.13%	Capability fact, not a failure
Agent error	0	0.00%	Ours, never the provider
Measurement error	0	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.

PublicNode 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

PublicNode 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 PublicNode 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

DegradedgetLatestBlockhashon Solana2026-10-08 07:465m
DegradedgetLatestBlockhashon Solana2026-10-08 03:2413m
DegradedgetLatestBlockhashon Solana2026-10-07 23:2610m
DegradedgetLatestBlockhashon Solana2026-10-07 23:1112m
DegradedgetSloton Solana2026-10-07 19:3011m
DegradedgetSloton Solana2026-10-07 17:457m

Persistent conditions

None. Every call measured on PublicNode succeeded often enough, often enough of the time, not to qualify.

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.

PublicNode broken out by region
Region	Median	p95	p99	Success	Rate limited	Samples
Coventry	37.0 ms	65.7 ms	201 ms	98.7%	—	30,143
Frankfurt	16.7 ms	39.5 ms	180 ms	98.7%	—	30,167
Virginia	17.0 ms	34.2 ms	83.9 ms	98.7%	—	30,187
Amsterdam	27.2 ms	51.3 ms	186 ms	98.7%	—	30,196

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-rpc.publicnode.com	keyless
BSC	ws_jsonrpc	wss://bsc-rpc.publicnode.com	keyless
Ethereum	http_jsonrpc	https://ethereum-rpc.publicnode.com	keyless
Ethereum	ws_jsonrpc	wss://ethereum-rpc.publicnode.com	keyless
Solana	http_jsonrpc	https://solana-rpc.publicnode.com	keyless
Solana	ws_jsonrpc	wss://solana-rpc.publicnode.com	keyless

Embed this

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

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

HTML

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