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
24h window · 24 hours observed · generated 2026-08-27 07:02:40 UTC
| Metric | dRPC | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 3 | 5 | 9 |
| Score | 90.8 | 83.8 | 52.3 |
| Status | Excellent | Good | Degraded |
| Availability | 99.91% | 99.98% | 23.13% |
| p50 latency | 34.2 ms | 105.0 ms | 15.9 ms |
| p95 latency | 70.2 ms | 122.0 ms | 92.8 ms |
| p99 latency | 173.1 ms | 144.5 ms | 243.9 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.38 blocks | 0.42 blocks | no cohort |
| Rate limited | 138 | 344 | 36 |
| Unsupported | 0 | 0 | 1,101 |
| Samples | 36,716 | 37,089 | 37,265 |
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.0points
- Latency+7.0
- Head freshness+0.0
- Availability−0.0
- Correctness+0.0
The parts add to +7.0, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+38.6points
- Availability+29.7
- Head freshness*+9.5
- Correctness−2.2
- Latency+1.6
The parts add to +38.6, 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.