Network

Ethereum

ETH · chain id 1 · 12000 ms block time · 9 providers, 12 endpoints

Just tell meWhich Ethereum provider leadsThe ranking below, read as an answer — with the figures behind it and what it refuses to claim.Before you payDo you need a dedicated node?What the free endpoints actually manage, and how often they refuse. Often the answer is no.

Proof-of-stake finality is reached after two justified epochs, roughly 12.8 minutes. Freshness is measured against the latest execution head, which reorgs are expected to affect.

Provider ranking

24h window · 24 hours observed · 4 vantage points · generated 2026-10-28 22:04:17 UTC

Excellent / Good— Fast, available and correct all window
Fair / Degraded— Measurable failures or slow tails
Poor— Failing often enough to affect an application
Insufficient data— Too few samples to score at all

1 (1st)
Provider
Tenderly
Score
99.5
Status
Excellent
Availability
100.0%
p50 ms
26.7
p95 ms
47.9
Trend
−7%
Correct
100.0%
Behind
0.42
Samples
37,368
2 (2nd)
Provider
PublicNode
Score
96.2
Status
Excellent
Availability
99.9%
p50 ms
28.3
p95 ms
61.3
Trend
+12%
Correct
100.0%
Behind
0.45
Samples
37,669
3 (3rd)
Provider
NodeReal
Score
85.2
Status
Good
Availability
100.0%
p50 ms
87.0
p95 ms
99.2
Trend
steady
Correct
100.0%
Behind
0.36
Samples
36,734
4
Provider
Blast API
Score
80.4
Status
Good
Availability
99.9%
p50 ms
104.9
p95 ms
122.1
Trend
steady
Correct
100.0%
Behind
0.41
Samples
35,844
5
Provider
dRPC
Score
79.8
Status
Good
Availability
99.9%
p50 ms
41.9
p95 ms
125.2
Trend
+7%
Correct
100.0%
Behind
0.36
Samples
35,127
6
Provider
MEV Blocker
Score
77.5
Status
Good
Availability
99.7%
p50 ms
46.6
p95 ms
138.0
Trend
+8%
Correct
100.0%
Behind
0.43
Samples
37,392
7
Provider
Merkle
Score
68.3
Status
Degraded
Availability
97.1%
p50 ms
111.7
p95 ms
207.0
Trend
−15%
Correct
100.0%
Behind
0.44
Samples
7,388
8
Provider
1RPConerpc
Score
56.0
Status
Degraded
Availability
69.2%
p50 ms
348.0
p95 ms
1883.1
Trend
not enough history
Correct
96.6%
Behind
0.79
Samples
7,696
9
Provider
Cloudflare
Score
44.2
Status
Poor
Availability
23.4%
p50 ms
21.2
p95 ms
124.8
Trend
−25%
Correct
100.0%
Behind
—
Samples
32,566

Provider ranking by composite score
#	Provider	Score	Status	Availability	p50 ms	p95 ms	Trend	Correct	Behind	Samples
1 (1st)	Tenderly	99.5	Excellent	100.0%	26.7	47.9	−7%	100.0%	0.42	37,368
2 (2nd)	PublicNode	96.2	Excellent	99.9%	28.3	61.3	+12%	100.0%	0.45	37,669
3 (3rd)	NodeReal	85.2	Good	100.0%	87.0	99.2	steady	100.0%	0.36	36,734
4	Blast API	80.4	Good	99.9%	104.9	122.1	steady	100.0%	0.41	35,844
5	dRPC	79.8	Good	99.9%	41.9	125.2	+7%	100.0%	0.36	35,127
6	MEV Blocker	77.5	Good	99.7%	46.6	138.0	+8%	100.0%	0.43	37,392
7	Merkle	68.3	Degraded	97.1%	111.7	207.0	−15%	100.0%	0.44	7,388
8	1RPConerpc	56.0	Degraded	69.2%	348.0	1883.1	not enough history	96.6%	0.79	7,696
9	Cloudflare	44.2	Poor	23.4%	21.2	124.8	−25%	100.0%	—	32,566

Take it awayCSV JSONevery provider in this window, with each score component

nodereal — 4 of 36734 requests were rate limited; excluded from availability
blastapi — 1% of requests were rate limited (462 of 35836); excluded from availability
drpc — 2% of requests were rate limited (563 of 35116); excluded from availability
merkle — 95% of requests were rate limited (6182 of 6523); excluded from availability
onerpc — 93% of requests were rate limited (6337 of 6791); excluded from availability
cloudflare — 3% of requests were rate limited (885 of 31167); excluded from availability

9 providers scored against each other.

The score weights availability at 40%, latency at 30%, correctness at 20% and head freshness at 10%. Correctness also acts as a ceiling: a provider that answers quickly and wrongly cannot be rated healthy on speed alone. Full methodology

Latency over time

24h window · top 6 by score

95th percentile, computed over successful requests only. A request that timed out is not a latency sample; it is counted against availability instead. Gaps are gaps — periods with no collection are not bridged.

Head freshness

24h window · generated 2026-10-28 22:04:22 UTC · cohort of 8

How far behind the chain each provider's data is. Latency cannot answer this: an endpoint can reply in 8 ms with a head from four minutes ago, and every speed measurement will still rate it excellent.

Providers ranked by distance behind the cohort head
#	Provider	Mean blocks behind	≈ seconds	Worst blocks	Compared
1 (1st)	nodereal	0.36	4.33	3	15,900
2 (2nd)	drpc	0.36	4.36	3	14,678
3 (3rd)	blastapi	0.41	4.87	3	15,176
4	tenderly	0.42	5.09	3	16,309
5	mevblocker	0.43	5.14	3	16,255
6	merkle	0.44	5.28	2	50
7	publicnode	0.45	5.42	3	16,503
8	onerpc	0.79	9.51	2	130

Each observed head is compared against the cohort reference for its instant: the highest head any measured provider had reached, after discarding heads implausibly far above the cohort median and time-aligning samples taken moments apart. Lag is therefore relative to the fastest-updating provider in the set, not to an absolute truth. A cohort of fewer than two providers produces no freshness data at all.

From each region

The same Ethereum measurements, grouped by the vantage point they were taken from. A provider that answers in 40 ms from one region can take 220 ms from another, and the ranking above is an average across whichever regions are reporting.

Ethereum broken out by region
Region	Median	p95	p99	Success	Rate limited	Samples
Coventry	50.4 ms	121 ms	262 ms	82.8%	3,507	67,818
Amsterdam	40.9 ms	113 ms	163 ms	84.3%	3,575	67,212
Frankfurt	29.2 ms	115 ms	167 ms	86.1%	4,159	63,982
Virginia	28.5 ms	130 ms	249 ms	83.4%	3,194	68,804

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