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
24h window · 24 hours observed · generated 2026-08-27 08:51:24 UTC
| Metric | dRPC | Blast API | 1RPC |
|---|---|---|---|
| Rank | 3 | 5 | 8 |
| Score | 90.7 | 83.8 | 58.2 |
| Status | Excellent | Good | Degraded |
| Availability | 99.92% | 99.99% | 74.93% |
| p50 latency | 34.2 ms | 105.2 ms | 2024.4 ms |
| p95 latency | 70.7 ms | 122.2 ms | 6590.4 ms |
| p99 latency | 173.5 ms | 145.6 ms | 9196.2 ms |
| Correctness | 99.99% | 99.99% | 96.63% |
| Head lag | 0.38 blocks | 0.42 blocks | 0.95 blocks |
| Rate limited | 149 | 394 | 6,629 |
| Unsupported | 0 | 0 | 0 |
| Samples | 38,018 | 38,418 | 7,950 |
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 dRPC, the highest scorer of those selected.
dRPCvsBlast API
+6.9points
- Latency+6.9
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +6.9, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+32.5points
- Latency+21.2
- Availability+10.0
- Correctness+0.7
- Head freshness+0.7
The parts add to +32.5, exactly — the score is a weighted sum, so it comes apart.