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
1h window · 60 minutes observed · generated 2026-08-27 12:25:41 UTC
| Metric | Tenderly | dRPC | Blast API |
|---|---|---|---|
| Rank | 1 | 3 | 5 |
| Score | 99.4 | 86.7 | 78.2 |
| Status | Excellent | Good | Good |
| Availability | 100.00% | 99.94% | 100.00% |
| p50 latency | 20.8 ms | 34.0 ms | 108.4 ms |
| p95 latency | 34.2 ms | 80.0 ms | 128.4 ms |
| p99 latency | 66.4 ms | 193.6 ms | 158.8 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.38 blocks | 0.41 blocks |
| Rate limited | 0 | 10 | 10 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,616 | 1,587 | 1,613 |
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
+12.7points
- Latency+12.8
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +12.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+21.2points
- Latency+21.3
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.2, exactly — the score is a weighted sum, so it comes apart.