Providers
Compare RPC providers on measured data
The top 4 on the chosen chain are compared by default. Pick your own — up to 4 — and the selection moves into the URL, so a comparison can be sent to someone else and they will see exactly what you saw.
Providers on Ethereum
Side by side
24h window · 24 hours observed · generated 2026-08-26 15:59:11 UTC
| Metric | Tenderly | dRPC | Blast API |
|---|---|---|---|
| Rank | 2 | 3 | 5 |
| Score | 94.8 | 93.2 | 85.5 |
| Status | Excellent | Excellent | Good |
| Availability | 99.95% | 99.96% | 99.97% |
| p50 latency | 20.3 ms | 34.2 ms | 104.3 ms |
| p95 latency | 61.3 ms | 69.6 ms | 121.6 ms |
| p99 latency | 852.7 ms | 170.6 ms | 141.9 ms |
| Correctness | 99.98% | 99.99% | 99.97% |
| Head lag | 0.50 blocks | 0.36 blocks | 0.42 blocks |
| Rate limited | 0 | 114 | 304 |
| Unsupported | 0 | 0 | 0 |
| Samples | 38,920 | 38,263 | 38,840 |
9 providers scored against each other.
Where the gap comes from
Two scores side by side say one is higher. This says why: the score is a weighted sum, so it comes apart, and each component’s share of the difference adds back to the difference exactly. Compared against Tenderly, the highest scorer of those selected.
TenderlyvsdRPC
+1.6points
- Latency+1.8
- Head freshness−0.2
- Correctness−0.0
- Availability−0.0
The parts add to +1.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+9.3points
- Latency+9.4
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +9.3, exactly — the score is a weighted sum, so it comes apart.