Skip to content

Ethereum method

eth_maxPriorityFeePerGas

How each provider handles it

9 providers

Provider support for eth_maxPriorityFeePerGas on Ethereum
ProviderStatusSuccessMedian
PublicNodeSupported100.0%19 ms
TenderlySupported100.0%19 ms
dRPCSupported100.0%36 ms
MEV BlockerSupported99.3%45 ms
NodeRealSupported100.0%87 ms
CloudflareNot implemented0.0%
Blast APIDegraded98.9%105 ms
MerkleRate limited25.9%105 ms
1RPConerpcRate limited10.0%422 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.

Blast API

  • success fell to 93.3% from a typical 100.0%

    availability · 2026-08-26 01:00Z

Merkle

  • success fell to 17.4% from a typical 26.1%

    availability · 2026-08-25 20:00Z

  • success fell to 16.7% from a typical 26.1%

    availability · 2026-08-25 22:00Z

1RPC

  • success fell to 0.0% from a typical 48.4%

    availability · 2026-08-25 20:00Z2026-08-25 23:00Z

  • success fell to 0.0% from a typical 48.4%

    availability · 2026-08-26 01:00Z

6h window · generated 2026-08-26 01:56:48 UTC · 9 providers