Ethereum method

eth_gasPrice

Returns the node's estimate of a reasonable gas price, in wei.

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_gasPrice on Ethereum
Provider	Status	Success	Median	Worst p95	Incidents	Samples
1RPConerpc	Rate limited	0.0%	—	—	none	23
Cloudflare	Failing	0.0%	—	—	none	119
Tenderly	Supported	100.0%	22 ms	44 ms	none	115
NodeReal	Supported	100.0%	73 ms	106 ms	none	113
Merkle	Rate limited	8.7%	68 ms	111 ms	none	23
MEV Blocker	Supported	100.0%	51 ms	150 ms	none	117
Blast API	Supported	100.0%	91 ms	185 ms	none	116
dRPC	Degraded	98.3%	54 ms	384 ms	none	115
PublicNode	Supported	100.0%	25 ms	550 ms	none	118

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 minute. 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. 2 providers are not plotted: they returned no successful response in this window, so they have no latency.

What it does

An estimate, not a fact. Each client computes it differently — commonly the median of recent blocks — so two correct nodes will return different numbers at the same instant, and neither is wrong.

Since EIP-1559 it is mostly a legacy convenience. Applications that care about fees read `eth_feeHistory` and compute a base fee and priority fee themselves.

Returns

QUANTITY — gas price in wei, in hex.

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_gasPrice","params":[],"id":73}'

As JSON-RPC

{
  "jsonrpc": "2.0",
  "method": "eth_gasPrice",
  "params": [],
  "id": 73
}

Response

{
  "id": 73,
  "jsonrpc": "2.0",
  "result": "0x1dfd14000"
}

Things that bite

Different providers returning different values here is expected behaviour and is never scored as a correctness failure on this platform.

Why it is measured

A cheap call whose answer requires the node to have recent blocks indexed, so it sits between the pure-constant methods and the real state reads.

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

1h window · generated 2026-10-08 18:13:04 UTC · 9 providers