Ethereum method
eth_estimateGas
How each provider handles it
| Provider | Status | Success | Median |
|---|---|---|---|
| Tenderly | Supported | 100.0% | 18 ms |
| PublicNode | Supported | 99.6% | 19 ms |
| dRPC | Supported | 100.0% | 45 ms |
| MEV Blocker | Supported | 100.0% | 45 ms |
| Cloudflare | Supported | 100.0% | 59 ms |
| NodeReal | Supported | 99.6% | 87 ms |
| Blast API | Supported | 99.6% | 104 ms |
| Merkle | Rate limited | 21.3% | 100 ms |
| 1RPConerpc | Rate limited | 10.3% | 4538 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.
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 11.5% from a typical 20.7%
availability · 2026-08-28 02:00Z
1RPC
success fell to 0.0% from a typical 42.4%
availability · 2026-08-27 23:00Z
success fell to 0.0% from a typical 42.4%
availability · 2026-08-28 01:00Z → 2026-08-28 03:00Z
6h window · generated 2026-08-28 04:25:25 UTC · 9 providers