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 22:38:58 UTC
| Metric | dRPC | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 3 | 5 | 8 |
| Score | 88.5 | 78.3 | 48.1 |
| Status | Good | Good | Poor |
| Availability | 99.99% | 99.92% | 23.09% |
| p50 latency | 34.3 ms | 107.7 ms | 16.4 ms |
| p95 latency | 70.4 ms | 125.4 ms | 93.0 ms |
| p99 latency | 192.1 ms | 152.5 ms | 271.9 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.36 blocks | 0.40 blocks | no cohort |
| Rate limited | 19 | 44 | 15 |
| Unsupported | 0 | 0 | 269 |
| Samples | 9,015 | 9,140 | 9,143 |
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
+10.2points
- Latency+10.1
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +10.2, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+40.4points
- Availability+29.7
- Head freshness*+9.6
- Latency+3.3
- Correctness−2.2
The parts add to +40.4, 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.