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 03:22:48 UTC
| Metric | dRPC | Blast API | 1RPC |
|---|---|---|---|
| Rank | 3 | 5 | 8 |
| Score | 91.2 | 83.5 | 60.3 |
| Status | Excellent | Good | Degraded |
| Availability | 99.98% | 99.99% | 79.94% |
| p50 latency | 32.5 ms | 103.9 ms | 1326.0 ms |
| p95 latency | 62.5 ms | 119.2 ms | 7406.7 ms |
| p99 latency | 163.8 ms | 147.2 ms | 9776.0 ms |
| Correctness | 99.98% | 99.99% | 96.96% |
| Head lag | 0.37 blocks | 0.41 blocks | 0.94 blocks |
| Rate limited | 7 | 32 | 1,461 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,577 | 8,718 | 2,023 |
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
+7.7points
- Latency+7.6
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +7.7, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+30.9points
- Latency+21.7
- Availability+8.0
- Head freshness+0.6
- Correctness+0.6
The parts add to +30.9, exactly — the score is a weighted sum, so it comes apart.