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 14:29:33 UTC
| Metric | dRPC | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 3 | 5 | 8 |
| Score | 88.2 | 78.6 | 48.5 |
| Status | Good | Good | Poor |
| Availability | 99.95% | 99.99% | 23.16% |
| p50 latency | 34.0 ms | 108.1 ms | 16.3 ms |
| p95 latency | 73.8 ms | 125.7 ms | 93.4 ms |
| p99 latency | 174.0 ms | 153.2 ms | 134.5 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.36 blocks | 0.41 blocks | no cohort |
| Rate limited | 37 | 58 | 12 |
| Unsupported | 0 | 0 | 258 |
| Samples | 8,754 | 8,893 | 8,901 |
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
+9.6points
- Latency+9.6
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +9.6, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+39.7points
- Availability+29.7
- Head freshness*+9.6
- Latency+2.6
- Correctness−2.2
The parts add to +39.7, exactly — the score is a weighted sum, so it comes apart. Components marked * were measured for only one of the two; the other’s weight is spread across what it does have, which is why the two sides can carry different weights for the same row.