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
30d window · 2.8 days observed · generated 2026-08-27 16:06:19 UTC
| Metric | Tenderly | dRPC | Blast API | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 3 | 5 | 8 |
| Score | 96.4 | 92.2 | 84.9 | 62.4 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 99.96% | 99.93% | 99.98% | 84.99% |
| p50 latency | 19.8 ms | 33.8 ms | 105.0 ms | 225.7 ms |
| p95 latency | 51.8 ms | 71.8 ms | 122.5 ms | 4391.3 ms |
| p99 latency | 759.0 ms | 169.5 ms | 147.0 ms | 7602.5 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 97.48% |
| Head lag | 0.50 blocks | 0.36 blocks | 0.42 blocks | 0.91 blocks |
| Rate limited | 0 | 645 | 1,180 | 18,765 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 109,276 | 107,462 | 108,703 | 22,905 |
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
+4.3points
- Latency+4.4
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +4.3, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+11.5points
- Latency+11.6
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +11.5, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+34.0points
- Latency+27.0
- Availability+6.0
- Correctness+0.5
- Head freshness+0.5
The parts add to +34.0, exactly — the score is a weighted sum, so it comes apart.