Skip to content

Ethereum method

eth_maxPriorityFeePerGas

How each provider handles it

9 providers

Provider support for eth_maxPriorityFeePerGas on Ethereum
ProviderStatusSuccessMedian
1RPConerpcRate limited0.0%
CloudflareNot implemented0.0%
PublicNodeSupported100.0%18 ms
NodeRealSupported100.0%86 ms
dRPCSupported100.0%47 ms
Blast APIDegraded94.7%106 ms
MEV BlockerSupported100.0%48 ms
MerkleRate limited19.6%111 ms
TenderlySupported100.0%21 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. 2 providers are 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

  • median rose to 108ms from a typical 36ms

    latency · 2026-08-25 10:00Z

Blast API

  • success fell to 93.6% from a typical 100.0%

    availability · 2026-08-25 08:00Z2026-08-25 09:00Z

  • success fell to 91.3% from a typical 100.0%

    availability · 2026-08-25 11:00Z

Merkle

  • success fell to 11.5% from a typical 20.0%

    availability · 2026-08-25 12:00Z

6h window · generated 2026-08-25 13:37:18 UTC · 9 providers