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

6h window · 6.0 hours observed · 4 vantage points · generated 2026-10-28 20:31:42 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
9.3
p95 ms
18.7
Trend
−12%
Correct
100.0%
Behind
0.45
Samples
2,239
2 (2nd)
Provider
PublicNode
Score
92.4
Status
Excellent
Availability
100.0%
p50 ms
20.8
p95 ms
43.5
Trend
+65%
Correct
100.0%
Behind
0.46
Samples
2,247
3 (3rd)
Provider
NodeReal
Score
79.4
Status
Good
Availability
100.0%
p50 ms
95.9
p95 ms
101.6
Trend
steady
Correct
100.0%
Behind
0.40
Samples
2,194
4
Provider
MEV Blocker
Score
77.1
Status
Good
Availability
99.6%
p50 ms
32.8
p95 ms
116.8
Trend
steady
Correct
100.0%
Behind
0.44
Samples
2,238
5
Provider
dRPC
Score
75.3
Status
Good
Availability
100.0%
p50 ms
36.9
p95 ms
133.0
Trend
−15%
Correct
100.0%
Behind
0.39
Samples
2,164
6
Provider
Blast API
Score
74.9
Status
Degraded
Availability
100.0%
p50 ms
113.0
p95 ms
135.9
Trend
−8%
Correct
100.0%
Behind
0.43
Samples
1,962
7
Provider
Merkle
Score
69.7
Status
Degraded
Availability
100.0%
p50 ms
123.9
p95 ms
225.6
Trend
+36%
Correct
100.0%
Behind
0.25
Samples
440
8
Provider
Cloudflare
Score
39.1
Status
Poor
Availability
23.8%
p50 ms
23.1
p95 ms
134.5
Trend
−16%
Correct
100.0%
Behind
—
Samples
1,467
9
Provider
1RPConerpc
Score
0.0
Status
Poor
Availability
0.0%
p50 ms
0.0
p95 ms
0.0
Trend
not enough history
Correct
—
Behind
—
Samples
441

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%	9.3	18.7	−12%	100.0%	0.45	2,239
2 (2nd)	PublicNode	92.4	Excellent	100.0%	20.8	43.5	+65%	100.0%	0.46	2,247
3 (3rd)	NodeReal	79.4	Good	100.0%	95.9	101.6	steady	100.0%	0.40	2,194
4	MEV Blocker	77.1	Good	99.6%	32.8	116.8	steady	100.0%	0.44	2,238
5	dRPC	75.3	Good	100.0%	36.9	133.0	−15%	100.0%	0.39	2,164
6	Blast API	74.9	Degraded	100.0%	113.0	135.9	−8%	100.0%	0.43	1,962
7	Merkle	69.7	Degraded	100.0%	123.9	225.6	+36%	100.0%	0.25	440
8	Cloudflare	39.1	Poor	23.8%	23.1	134.5	−16%	100.0%	—	1,467
9	1RPConerpc	0.0	Poor	0.0%	0.0	0.0	not enough history	—	—	441

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

drpc — 2% of requests were rate limited (34 of 2163); excluded from availability
blastapi — 3% of requests were rate limited (54 of 1961); excluded from availability
merkle — 93% of requests were rate limited (361 of 387); excluded from availability
cloudflare — 10% of requests were rate limited (136 of 1393); excluded from availability
onerpc — 99% of requests were rate limited (382 of 385); 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

6h 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

6h window · generated 2026-10-28 21:23:04 UTC · cohort of 7

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)	drpc	0.37	4.42	2	3,590
2 (2nd)	nodereal	0.39	4.64	2	3,711
3 (3rd)	blastapi	0.41	4.90	3	3,313
4	tenderly	0.42	5.01	2	3,806
5	mevblocker	0.43	5.15	3	3,782
6	merkle	0.44	5.33	1	9
7	publicnode	0.45	5.45	3	3,831

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	42.8 ms	153 ms	320 ms	83.4%	734	16,069
Amsterdam	45.9 ms	114 ms	164 ms	83.4%	773	16,030
Coventry	55.3 ms	129 ms	258 ms	82.0%	889	15,494
Frankfurt	33.5 ms	120 ms	176 ms	86.0%	937	15,079

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