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
1h window · 60 minutes observed · generated 2026-08-28 01:25:36 UTC
| Metric | Tenderly | dRPC | Blast API | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 3 | 5 | 8 |
| Score | 98.7 | 90.8 | 83.3 | 62.7 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 100.00% | 99.87% | 99.94% | 83.33% |
| p50 latency | 19.5 ms | 33.1 ms | 103.4 ms | 1688.5 ms |
| p95 latency | 32.6 ms | 63.4 ms | 119.3 ms | 3180.4 ms |
| p99 latency | 53.3 ms | 207.5 ms | 145.9 ms | 3180.4 ms |
| Correctness | 100.00% | 99.87% | 99.94% | 100.00% |
| Head lag | 0.47 blocks | 0.39 blocks | 0.41 blocks | 0.50 blocks |
| Rate limited | 0 | 3 | 23 | 322 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 1,603 | 1,580 | 1,616 | 367 |
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.9points
- Latency+7.9
- Head freshness−0.1
- Availability+0.1
- Correctness+0.0
The parts add to +7.9, 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.
Tenderlyvs1RPC
+35.9points
- Latency+29.2
- Availability+6.7
- Head freshness+0.0
- Correctness+0.0
The parts add to +35.9, exactly — the score is a weighted sum, so it comes apart.