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 14:13:01 UTC
| Metric | Tenderly | dRPC | Blast API |
|---|---|---|---|
| Rank | 1 | 3 | 5 |
| Score | 99.4 | 90.6 | 83.8 |
| Status | Excellent | Excellent | Good |
| Availability | 99.98% | 99.92% | 99.99% |
| p50 latency | 19.2 ms | 33.9 ms | 105.7 ms |
| p95 latency | 34.1 ms | 71.8 ms | 122.0 ms |
| p99 latency | 77.0 ms | 172.0 ms | 148.4 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.37 blocks | 0.41 blocks |
| Rate limited | 0 | 147 | 331 |
| Unsupported | 0 | 0 | 0 |
| Samples | 37,567 | 36,996 | 37,383 |
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
+8.8points
- Latency+9.0
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.8, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+15.6points
- Latency+15.7
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +15.6, exactly — the score is a weighted sum, so it comes apart.