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 05:30:25 UTC
| Metric | Tenderly | dRPC | Blast API |
|---|---|---|---|
| Rank | 2 | 3 | 5 |
| Score | 99.2 | 91.2 | 83.8 |
| Status | Excellent | Excellent | Good |
| Availability | 100.00% | 99.98% | 99.99% |
| p50 latency | 17.9 ms | 32.0 ms | 103.7 ms |
| p95 latency | 30.7 ms | 62.1 ms | 117.3 ms |
| p99 latency | 52.3 ms | 178.5 ms | 143.0 ms |
| Correctness | 100.00% | 99.98% | 99.99% |
| Head lag | 0.47 blocks | 0.37 blocks | 0.40 blocks |
| Rate limited | 0 | 9 | 42 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,924 | 8,783 | 8,927 |
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.1points
- Latency+8.2
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.1, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+15.4points
- Latency+15.5
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +15.4, exactly — the score is a weighted sum, so it comes apart.