Ethereum method
eth_estimateGas
How each provider handles it
| Provider | Status | Success | Median |
|---|---|---|---|
| 1RPConerpc | Rate limited | 1.7% | 1514 ms |
| Cloudflare | Supported | 99.1% | 82 ms |
| Merkle | Rate limited | 4.9% | 108 ms |
| dRPC | Degraded | 98.7% | 49 ms |
| Blast API | Supported | 99.1% | 104 ms |
| MEV Blocker | Supported | 99.8% | 49 ms |
| PublicNode | Supported | 100.0% | 24 ms |
| NodeReal | Supported | 99.9% | 88 ms |
| Tenderly | Supported | 100.0% | 26 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.
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.
Cloudflare
success fell to 94.2% from a typical 99.7%
availability · 2026-10-28 00:00Z
1RPC
median rose to 2616ms from a typical 769ms
latency · 2026-09-29 00:00Z
median rose to 7136ms from a typical 769ms
latency · 2026-10-01 00:00Z → 2026-10-03 00:00Z
median rose to 3768ms from a typical 769ms
latency · 2026-10-06 00:00Z
median rose to 5011ms from a typical 769ms
latency · 2026-10-09 00:00Z → 2026-10-11 00:00Z
30d window · generated 2026-10-28 22:54:07 UTC · 9 providers