Providers

dRPCGood

Decentralised RPC aggregator routing across a provider network. The free public tier is rate limited.

commercial · rank 6 of 12

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

Measured performance

24h window · 24 hours observed · 1 chain

Composite score

78.7

Rank 6 of 12

36,721 samples

Availability

99.98%

Rate limits and unsupported methods excluded

Latency p95

125.3ms

p50 35.4 · p99 245.9

Correctness

99.99%

36,298 responses judged

1% of requests were rate limited (419 of 36718); 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.98 %	100.0	Share of requests that succeeded, excluding rate limits and unsupported methods.
Latency	30%	125.27 ms	30.6	Scored on p95 relative to the cohort, log-scaled so a 10x difference is not a 10x penalty.
Correctness	20%	99.99 %	100.0	Share of responses that were valid. Also caps the overall score, so speed cannot compensate for wrong answers.
Head freshness	10%	0.41 blocks behind	95.0	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	36,293	98.83%	—
Provider failure	424	1.15%	Counted against provider
Network failure	1	0.00%	Counted against provider
Rate limited	419	1.14%	Excluded from availability
Unsupported method	0	0.00%	Capability fact, not a failure
Agent error	0	0.00%	Ours, never the provider
Measurement error	3	0.01%	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.

dRPC 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

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

Throttledeth_blockNumberon Ethereum2026-10-08 17:1513m
Throttledeth_blockNumberon Ethereum2026-10-08 16:557m
Throttledeth_blockNumberon Ethereum2026-10-08 16:4815m
Throttledeth_chainIdon Ethereum2026-10-08 16:013m
Throttledeth_getBlockByNumberon Ethereum2026-10-08 15:5818m
Throttledeth_getTransactionCounton Ethereum2026-10-08 15:5216m
Throttledeth_blockNumberon Ethereum2026-10-08 15:459m
Throttledeth_estimateGason Ethereum2026-10-08 15:4510m

14 more. All incidents

Persistent conditions

None. Every call measured on dRPC 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.

dRPC broken out by region
Region	Median	p95	p99	Success	Rate limited	Samples
Frankfurt	25.7 ms	132 ms	257 ms	98.7%	117	9,209
Amsterdam	32.5 ms	131 ms	261 ms	98.4%	144	9,195
Virginia	32.9 ms	71.1 ms	130 ms	100.0%	—	9,270
Coventry	45.3 ms	157 ms	284 ms	98.2%	158	9,047

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.drpc.org	keyless
Ethereum	http_jsonrpc	https://eth.drpc.org	keyless
Ethereum	ws_jsonrpc	wss://eth.drpc.org	keyless

Embed this

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

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

HTML

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