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

30d window · 30.0 days observed · 4 vantage points · generated 2026-10-28 21:23:28 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.4
Status
Excellent
Availability
100.0%
p50 ms
28.8
p95 ms
41.5
Trend
steady
Correct
100.0%
Behind
0.47
Samples
290,727
2 (2nd)
Provider
PublicNode
Score
93.6
Status
Excellent
Availability
100.0%
p50 ms
33.8
p95 ms
64.5
Trend
+24%
Correct
100.0%
Behind
0.45
Samples
292,745
3 (3rd)
Provider
NodeReal
Score
83.4
Status
Good
Availability
99.9%
p50 ms
85.1
p95 ms
98.2
Trend
steady
Correct
100.0%
Behind
0.35
Samples
285,589
4
Provider
MEV Blocker
Score
82.0
Status
Good
Availability
99.8%
p50 ms
45.2
p95 ms
103.7
Trend
steady
Correct
100.0%
Behind
0.42
Samples
290,543
5
Provider
dRPC
Score
81.9
Status
Good
Availability
100.0%
p50 ms
44.7
p95 ms
104.7
Trend
+67%
Correct
100.0%
Behind
0.40
Samples
282,601
6
Provider
Blast API
Score
78.5
Status
Good
Availability
100.0%
p50 ms
101.8
p95 ms
120.1
Trend
steady
Correct
100.0%
Behind
0.40
Samples
286,040
7
Provider
Merkle
Score
69.1
Status
Degraded
Availability
99.3%
p50 ms
109.1
p95 ms
208.5
Trend
+9%
Correct
100.0%
Behind
0.48
Samples
57,341
8
Provider
Cloudflare
Score
52.2
Status
Degraded
Availability
23.1%
p50 ms
18.3
p95 ms
84.1
Trend
+22%
Correct
100.0%
Behind
—
Samples
287,917
9
Provider
1RPConerpc
Score
33.1
Status
Poor
Availability
11.5%
p50 ms
231.9
p95 ms
4698.2
Trend
−51%
Correct
97.7%
Behind
0.88
Samples
74,720

Provider ranking by composite score
#	Provider	Score	Status	Availability	p50 ms	p95 ms	Trend	Correct	Behind	Samples
1 (1st)	Tenderly	99.4	Excellent	100.0%	28.8	41.5	steady	100.0%	0.47	290,727
2 (2nd)	PublicNode	93.6	Excellent	100.0%	33.8	64.5	+24%	100.0%	0.45	292,745
3 (3rd)	NodeReal	83.4	Good	99.9%	85.1	98.2	steady	100.0%	0.35	285,589
4	MEV Blocker	82.0	Good	99.8%	45.2	103.7	steady	100.0%	0.42	290,543
5	dRPC	81.9	Good	100.0%	44.7	104.7	+67%	100.0%	0.40	282,601
6	Blast API	78.5	Good	100.0%	101.8	120.1	steady	100.0%	0.40	286,040
7	Merkle	69.1	Degraded	99.3%	109.1	208.5	+9%	100.0%	0.48	57,341
8	Cloudflare	52.2	Degraded	23.1%	18.3	84.1	+22%	100.0%	—	287,917
9	1RPConerpc	33.1	Poor	11.5%	231.9	4698.2	−51%	97.7%	0.88	74,720

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

mevblocker — 1 of 290543 requests were rate limited; excluded from availability
drpc — 1% of requests were rate limited (3980 of 282583); excluded from availability
blastapi — 1343 of 285998 requests were rate limited; excluded from availability
merkle — 95% of requests were rate limited (48177 of 50580); excluded from availability
cloudflare — 594 of 276476 requests were rate limited; excluded from availability
onerpc — 67% of requests were rate limited (45350 of 67236); 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

30d 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

30d window · generated 2026-10-28 21:23:16 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.35	4.22	4	493,871
2 (2nd)	drpc	0.39	4.69	4	483,784
3 (3rd)	blastapi	0.40	4.82	24	490,895
4	mevblocker	0.42	5.02	4	505,703
5	publicnode	0.45	5.42	5	512,767
6	tenderly	0.46	5.47	4	507,135
7	merkle	0.48	5.73	2	1,721
8	onerpc	0.89	10.71	9	4,480

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
Virginia	26.0 ms	125 ms	207 ms	83.1%	95,070	2,152,680
Coventry	46.1 ms	110 ms	181 ms	82.9%	99,444	2,148,218
Amsterdam	36.7 ms	115 ms	158 ms	82.8%	99,720	2,147,927
Frankfurt	27.0 ms	113 ms	160 ms	83.1%	104,232	2,128,985

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