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:23:11 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.9
p95 ms
50.1
Trend
steady
Correct
100.0%
Behind
0.42
Samples
8,733
2 (2nd)
Provider
PublicNode
Score
90.1
Status
Excellent
Availability
99.8%
p50 ms
38.1
p95 ms
92.5
Trend
+77%
Correct
100.0%
Behind
0.46
Samples
8,768
3 (3rd)
Provider
NodeReal
Score
88.2
Status
Good
Availability
100.0%
p50 ms
87.4
p95 ms
99.9
Trend
+7%
Correct
100.0%
Behind
0.38
Samples
8,567
4
Provider
Blast API
Score
80.5
Status
Good
Availability
99.8%
p50 ms
108.5
p95 ms
133.2
Trend
−5%
Correct
100.0%
Behind
0.42
Samples
7,924
5
Provider
dRPC
Score
78.4
Status
Good
Availability
99.8%
p50 ms
48.3
p95 ms
144.7
Trend
−32%
Correct
100.0%
Behind
0.37
Samples
8,416
6
Provider
MEV Blocker
Score
77.1
Status
Good
Availability
99.7%
p50 ms
54.3
p95 ms
151.3
Trend
steady
Correct
100.0%
Behind
0.43
Samples
8,722
7
Provider
Merkle
Score
67.8
Status
Degraded
Availability
95.1%
p50 ms
120.8
p95 ms
231.2
Trend
+58%
Correct
100.0%
Behind
0.14
Samples
1,719
8
Provider
Cloudflare
Score
42.1
Status
Poor
Availability
23.2%
p50 ms
27.4
p95 ms
146.4
Trend
steady
Correct
100.0%
Behind
—
Samples
7,957
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
1,723

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.9	50.1	steady	100.0%	0.42	8,733
2 (2nd)	PublicNode	90.1	Excellent	99.8%	38.1	92.5	+77%	100.0%	0.46	8,768
3 (3rd)	NodeReal	88.2	Good	100.0%	87.4	99.9	+7%	100.0%	0.38	8,567
4	Blast API	80.5	Good	99.8%	108.5	133.2	−5%	100.0%	0.42	7,924
5	dRPC	78.4	Good	99.8%	48.3	144.7	−32%	100.0%	0.37	8,416
6	MEV Blocker	77.1	Good	99.7%	54.3	151.3	steady	100.0%	0.43	8,722
7	Merkle	67.8	Degraded	95.1%	120.8	231.2	+58%	100.0%	0.14	1,719
8	Cloudflare	42.1	Poor	23.2%	27.4	146.4	steady	100.0%	—	7,957
9	1RPConerpc	0.0	Poor	0.0%	0.0	0.0	not enough history	—	—	1,723

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

blastapi — 2% of requests were rate limited (191 of 7920); excluded from availability
drpc — 1% of requests were rate limited (107 of 8415); excluded from availability
merkle — 95% of requests were rate limited (1441 of 1522); excluded from availability
cloudflare — 2% of requests were rate limited (136 of 7627); excluded from availability
onerpc — 99% of requests were rate limited (1486 of 1504); 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 20:19:21 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)	merkle	0.14	1.71	1	7
2 (2nd)	drpc	0.38	4.51	2	3,515
3 (3rd)	nodereal	0.38	4.52	2	3,666
4	blastapi	0.42	5.02	2	3,193
5	tenderly	0.42	5.08	3	3,763
6	mevblocker	0.43	5.17	3	3,740
7	publicnode	0.46	5.52	3	3,786

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.2 ms	149 ms	288 ms	83.4%	727	15,870
Amsterdam	46.1 ms	115 ms	182 ms	83.4%	777	15,856
Coventry	56.5 ms	132 ms	270 ms	81.8%	888	15,268
Frankfurt	34.5 ms	123 ms	191 ms	85.8%	936	14,774

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