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-27 12:59:40 UTC
| Metric | Tenderly | dRPC | Blast API |
|---|---|---|---|
| Rank | 1 | 3 | 5 |
| Score | 99.4 | 90.4 | 83.7 |
| Status | Excellent | Excellent | Good |
| Availability | 99.97% | 99.91% | 99.99% |
| p50 latency | 19.4 ms | 34.2 ms | 105.7 ms |
| p95 latency | 34.7 ms | 72.8 ms | 122.9 ms |
| p99 latency | 93.2 ms | 173.1 ms | 148.7 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.38 blocks | 0.41 blocks |
| Rate limited | 0 | 165 | 331 |
| Unsupported | 0 | 0 | 0 |
| Samples | 38,845 | 38,233 | 38,644 |
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
+9.0points
- Latency+9.1
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +9.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+15.7points
- Latency+15.8
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +15.7, exactly — the score is a weighted sum, so it comes apart.