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-27 14:21:54 UTC
| Metric | Tenderly | dRPC | Blast API |
|---|---|---|---|
| Rank | 1 | 3 | 5 |
| Score | 99.4 | 88.3 | 78.6 |
| Status | Excellent | Good | Good |
| Availability | 99.94% | 99.95% | 99.99% |
| p50 latency | 20.2 ms | 33.9 ms | 108.1 ms |
| p95 latency | 34.3 ms | 73.6 ms | 125.8 ms |
| p99 latency | 77.7 ms | 173.5 ms | 153.3 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.35 blocks | 0.41 blocks |
| Rate limited | 0 | 37 | 58 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,710 | 8,552 | 8,695 |
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.1points
- Latency+11.3
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +11.1, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+20.8points
- Latency+20.9
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +20.8, exactly — the score is a weighted sum, so it comes apart.