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
1h window · 60 minutes observed · generated 2026-08-26 20:18:59 UTC
| Metric | dRPC | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 3 | 5 | 8 |
| Score | 88.0 | 79.1 | 45.1 |
| Status | Good | Good | Poor |
| Availability | 99.94% | 100.00% | 23.02% |
| p50 latency | 36.9 ms | 107.3 ms | 18.7 ms |
| p95 latency | 74.5 ms | 123.1 ms | 111.2 ms |
| p99 latency | 191.4 ms | 137.5 ms | 248.8 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.39 blocks | 0.40 blocks | no cohort |
| Rate limited | 6 | 45 | 0 |
| Unsupported | 0 | 0 | 49 |
| Samples | 1,585 | 1,533 | 1,614 |
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
+8.9points
- Latency+8.9
- Availability−0.0
- Head freshness+0.0
- Correctness+0.0
The parts add to +8.9, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+42.9points
- Availability+29.7
- Head freshness*+9.5
- Latency+5.8
- Correctness−2.2
The parts add to +42.9, 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.