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
30d window · 2.7 days observed · generated 2026-08-27 13:52:54 UTC
| Metric | dRPC | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 3 | 5 | 9 |
| Score | 92.3 | 85.0 | 54.8 |
| Status | Excellent | Good | Degraded |
| Availability | 99.93% | 99.98% | 23.10% |
| p50 latency | 33.8 ms | 104.8 ms | 15.1 ms |
| p95 latency | 71.9 ms | 122.2 ms | 87.5 ms |
| p99 latency | 168.1 ms | 146.3 ms | 250.8 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.36 blocks | 0.42 blocks | no cohort |
| Rate limited | 641 | 1,154 | 96 |
| Unsupported | 0 | 0 | 3,105 |
| Samples | 103,927 | 105,103 | 105,489 |
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.3points
- Latency+7.2
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +7.3, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+37.5points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency+0.5
The parts add to +37.5, 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.