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 03:15:19 UTC
| Metric | Tenderly | dRPC | Blast API | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 3 | 5 | 8 |
| Score | 99.4 | 90.6 | 84.2 | 58.7 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 100.00% | 99.94% | 99.99% | 76.33% |
| p50 latency | 19.2 ms | 33.2 ms | 103.4 ms | 2024.4 ms |
| p95 latency | 32.8 ms | 69.7 ms | 117.3 ms | 6590.4 ms |
| p99 latency | 72.2 ms | 167.2 ms | 145.0 ms | 9196.2 ms |
| Correctness | 100.00% | 99.99% | 100.00% | 96.63% |
| Head lag | 0.48 blocks | 0.38 blocks | 0.41 blocks | 0.95 blocks |
| Rate limited | 0 | 27 | 71 | 1,438 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,480 | 8,381 | 8,457 | 2,008 |
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+8.9
- 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.2points
- Latency+15.3
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +15.2, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+40.7points
- Latency+30.0
- Availability+9.5
- Correctness+0.7
- Head freshness+0.5
The parts add to +40.7, exactly — the score is a weighted sum, so it comes apart.