Ethereum method
eth_maxPriorityFeePerGas
How each provider handles it
| Provider | Status | Success | Median |
|---|---|---|---|
| Tenderly | Supported | 100.0% | 20 ms |
| PublicNode | Supported | 99.9% | 18 ms |
| NodeReal | Supported | 99.6% | 87 ms |
| MEV Blocker | Supported | 99.9% | 46 ms |
| Merkle | Rate limited | 23.1% | 106 ms |
| dRPC | Supported | 100.0% | 36 ms |
| Cloudflare | Not implemented | 0.0% | — |
| Blast API | Degraded | 98.5% | 105 ms |
| 1RPConerpc | Rate limited | 4.4% | 505 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 day. 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.
30d window · generated 2026-08-26 05:50:43 UTC · 9 providers