Skip to content

Ethereum method

eth_maxPriorityFeePerGas

How each provider handles it

9 providers

Provider support for eth_maxPriorityFeePerGas on Ethereum
ProviderStatusSuccessMedian
CloudflareNot implemented0.0%
PublicNodeSupported100.0%15 ms
NodeRealDegraded98.8%87 ms
Blast APISupported99.4%104 ms
MEV BlockerSupported100.0%45 ms
dRPCSupported100.0%35 ms
MerkleRate limited24.9%88 ms
TenderlySupported100.0%18 ms
1RPConerpcRate limited7.6%442 ms

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.

NodeReal

  • success fell to 91.3% from a typical 100.0%

    availability · 2026-08-24 22:00Z

1RPC

  • success fell to 0.0% from a typical 40.6%

    availability · 2026-08-24 21:00Z2026-08-24 23:00Z

  • success fell to 0.0% from a typical 40.6%

    availability · 2026-08-25 01:00Z2026-08-25 06:00Z

24h window · generated 2026-08-25 07:38:00 UTC · 9 providers