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
30d window · 2.6 days observed · generated 2026-08-27 09:56:02 UTC
| Metric | Tenderly | dRPC | Blast API | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 3 | 5 | 8 |
| Score | 95.3 | 92.6 | 85.3 | 62.5 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 99.96% | 99.93% | 99.98% | 85.27% |
| p50 latency | 19.8 ms | 33.8 ms | 104.6 ms | 225.7 ms |
| p95 latency | 58.6 ms | 71.9 ms | 122.0 ms | 4391.3 ms |
| p99 latency | 812.3 ms | 167.7 ms | 145.4 ms | 7602.5 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 97.48% |
| Head lag | 0.50 blocks | 0.36 blocks | 0.42 blocks | 0.91 blocks |
| Rate limited | 0 | 615 | 1,114 | 17,040 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 99,257 | 97,631 | 98,707 | 20,928 |
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
+2.7points
- Latency+2.8
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +2.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+10.0points
- Latency+10.1
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +10.0, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+32.8points
- Latency+25.9
- Availability+5.9
- Correctness+0.5
- Head freshness+0.5
The parts add to +32.8, exactly — the score is a weighted sum, so it comes apart.