Ethereum method
eth_estimateGas
How each provider handles it
| Provider | Status | Success | Median |
|---|---|---|---|
| Merkle | Rate limited | 4.7% | 99 ms |
| 1RPConerpc | Rate limited | 0.0% | — |
| Cloudflare | Degraded | 96.0% | 120 ms |
| NodeReal | Supported | 100.0% | 88 ms |
| dRPC | Degraded | 97.3% | 75 ms |
| Blast API | Degraded | 96.9% | 107 ms |
| Tenderly | Supported | 100.0% | 27 ms |
| PublicNode | Supported | 99.6% | 36 ms |
| MEV Blocker | Supported | 99.2% | 57 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.
dRPC
success fell to 91.7% from a typical 97.9%
availability · 2026-10-28 16:00Z
Cloudflare
success fell to 90.9% from a typical 100.0%
availability · 2026-10-28 16:00Z → 2026-10-28 17:00Z
6h window · generated 2026-10-28 21:26:16 UTC · 9 providers