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 01:01:48 UTC
| Metric | Tenderly | dRPC | Blast API | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 3 | 5 | 8 |
| Score | 99.4 | 91.9 | 83.8 | 60.3 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 100.00% | 99.96% | 99.99% | 79.94% |
| p50 latency | 18.4 ms | 32.3 ms | 104.8 ms | 1326.0 ms |
| p95 latency | 31.7 ms | 62.3 ms | 120.8 ms | 7406.7 ms |
| p99 latency | 53.2 ms | 166.1 ms | 149.2 ms | 9776.0 ms |
| Correctness | 100.00% | 99.97% | 99.99% | 96.96% |
| Head lag | 0.46 blocks | 0.37 blocks | 0.41 blocks | 0.94 blocks |
| Rate limited | 0 | 11 | 30 | 1,379 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,159 | 8,001 | 8,140 | 1,929 |
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
+7.5points
- Latency+7.6
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +7.5, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+15.7points
- Latency+15.7
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +15.7, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+39.2points
- Latency+30.0
- Availability+8.0
- Correctness+0.6
- Head freshness+0.6
The parts add to +39.2, exactly — the score is a weighted sum, so it comes apart.