Ethereum method

eth_syncing

Reports whether the node is still catching up with the chain.

cheapCheap for a provider to serve — no state is read, or one key is.Primary specification

How each provider handles it

Provider support for eth_syncing on Ethereum
Provider	Status	Success	Median	Worst p95	Incidents	Samples
Blast API	Not measured	0.0%	—	—	none	34,136
1RPConerpc	Rate limited	1.1%	1495 ms	4987 ms	3	17,717
Merkle	Rate limited	13.9%	106 ms	238 ms	none	18,003
dRPC	Supported	99.7%	29 ms	81 ms	none	33,964
Cloudflare	Supported	99.7%	14 ms	34 ms	none	34,171
MEV Blocker	Supported	99.8%	37 ms	120 ms	none	34,161
NodeReal	Supported	99.9%	87 ms	139 ms	none	34,019
PublicNode	Supported	100.0%	21 ms	129 ms	none	34,223
Tenderly	Supported	100.0%	15 ms	33 ms	none	34,175

Success excludes calls the provider does not implement — an optional method a provider declines to offer is a capability fact, not a failure, and is never scored as one.

Over time

Median latency per day. Gaps are periods with no measurement, drawn as gaps rather than joined across — a line through missing data invents a measurement that was never taken.

Logarithmic scale — each gridline is ten times the one below it. Click a provider in the legend to hide it. 1 provider is not plotted: they returned no successful response in this window, so they have no latency.

When it degraded

A degradation is a bucket where a provider fell away from ITS OWN median for this method over the window, not from the cohort's. A provider that is consistently slower than its peers is not degraded — it is slower, which the ranking already says. Buckets with fewer than 20 samples are skipped, because a claim about a provider cannot rest on a handful of calls, and adjacent bad buckets are merged so one outage reads as one incident.

1RPC

median rose to 3060ms from a typical 1273ms
latency · 2026-09-09 00:00Z
median rose to 3898ms from a typical 1273ms
latency · 2026-09-16 00:00Z → 2026-09-17 00:00Z
median rose to 3040ms from a typical 1273ms
latency · 2026-09-19 00:00Z → 2026-09-23 00:00Z

What it does

Returns `false` when the node is synced, and an object with `startingBlock`, `currentBlock` and `highestBlock` when it is not.

A syncing node answers requests normally and quickly while serving state that is hours or days old. Nothing else in the JSON-RPC surface tells you this.

Returns

Object | false.

Try it

Runnable as written, against a keyless public endpoint. Nothing here needs an API key.

Request

curl -s https://ethereum-rpc.publicnode.com \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_syncing","params":[],"id":1}'

As JSON-RPC

{
  "jsonrpc": "2.0",
  "method": "eth_syncing",
  "params": [],
  "id": 1
}

Response

{
  "id": 1,
  "jsonrpc": "2.0",
  "result": false
}

Things that bite

Behind a load balancer this reflects whichever node answered, so false is not a promise about the fleet.
Clients may add fields beyond the documented three. Parsers that reject unknown keys break on some providers.

Why it is measured

It is the only self-reported health signal in the standard API, and it is worth recording precisely because a syncing node looks healthy on every other metric.

Called every 300 seconds per endpoint, with jitter so the fleet does not hit a provider in lockstep.

30d window · generated 2026-10-08 18:19:53 UTC · 9 providers