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
6h window · 6.0 hours observed · generated 2026-08-28 21:30:43 UTC
| Metric | Tenderly | dRPC | Blast API |
|---|---|---|---|
| Rank | 1 | 3 | 5 |
| Score | 99.4 | 88.2 | 78.0 |
| Status | Excellent | Good | Good |
| Availability | 99.99% | 99.99% | 99.99% |
| p50 latency | 19.2 ms | 35.5 ms | 108.1 ms |
| p95 latency | 33.3 ms | 68.7 ms | 124.7 ms |
| p99 latency | 71.1 ms | 177.4 ms | 142.3 ms |
| Correctness | 99.99% | 100.00% | 99.99% |
| Head lag | 0.50 blocks | 0.37 blocks | 0.42 blocks |
| Rate limited | 0 | 28 | 2 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,940 | 8,773 | 8,937 |
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
+11.2points
- Latency+11.4
- Head freshness−0.2
- Correctness−0.0
- Availability+0.0
The parts add to +11.2, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+21.4points
- Latency+21.5
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.4, exactly — the score is a weighted sum, so it comes apart.