Ethereum method
eth_maxPriorityFeePerGas
How each provider handles it
| Provider | Status | Success | Median |
|---|---|---|---|
| Tenderly | Supported | 100.0% | 23 ms |
| Merkle | Rate limited | 18.4% | 90 ms |
| MEV Blocker | Supported | 100.0% | 50 ms |
| Blast API | Supported | 99.6% | 108 ms |
| dRPC | Supported | 100.0% | 40 ms |
| NodeReal | Supported | 100.0% | 87 ms |
| PublicNode | Supported | 99.6% | 19 ms |
| 1RPConerpc | Rate limited | 0.0% | — |
| Cloudflare | Not implemented | 0.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. 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.
Merkle
success fell to 8.0% from a typical 20.0%
availability · 2026-08-25 16:00Z
6h window · generated 2026-08-25 19:02:24 UTC · 9 providers