Skip to content

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 (opens in a new tab)

How each provider handles it

9 providers

Provider support for eth_gasPrice on Ethereum
ProviderStatusSuccessMedian
TenderlySupported100.0%27 ms
Blast APISupported100.0%109 ms
PublicNodeSupported99.8%25 ms
MEV BlockerSupported99.7%48 ms
NodeRealSupported99.7%87 ms
dRPCDegraded96.8%64 ms
MerkleRate limited6.1%102 ms
1RPConerpcFailing3.1%264 ms
CloudflareFailing0.0%—

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 hour. 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.

dRPC

  • success fell to 92.7% from a typical 98.3%

    availability · 2026-10-08 15:00Z

Merkle

  • success fell to 0.0% from a typical 8.0%

    availability · 2026-10-08 16:00Z

1RPC

  • success fell to 0.0% from a typical 11.0%

    availability · 2026-10-08 14:00Z

  • success fell to 0.0% from a typical 11.0%

    availability · 2026-10-08 16:00Z → 2026-10-08 18:00Z

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.

6h window · generated 2026-10-08 19:23:18 UTC · 9 providers