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

No measurements in this window.

Either no probe has reported for this chain yet, or the window is shorter than the collection interval. Try a longer window.

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

Head freshness

1h window · generated 2026-10-28 22:03:59 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
7	merkle	1.00	12.00	1	4
6	publicnode	0.45	5.40	2	716
5	mevblocker	0.44	5.24	2	710
4	tenderly	0.43	5.16	2	709
3 (3rd)	blastapi	0.41	4.96	2	634
2 (2nd)	drpc	0.40	4.83	2	688
1 (1st)	nodereal	0.32	3.84	2	682

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	40.7 ms	131 ms	242 ms	83.5%	135	2,981
Amsterdam	41.9 ms	111 ms	138 ms	83.6%	139	2,977
Frankfurt	27.6 ms	108 ms	176 ms	83.3%	142	2,947
Coventry	51.6 ms	117 ms	252 ms	82.8%	154	2,936

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