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 04:04:19 UTC
| Metric | dRPC | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 3 | 5 | 9 |
| Score | 90.5 | 84.1 | 55.8 |
| Status | Excellent | Good | Degraded |
| Availability | 99.98% | 99.99% | 23.19% |
| p50 latency | 32.8 ms | 103.0 ms | 12.7 ms |
| p95 latency | 68.6 ms | 115.4 ms | 68.4 ms |
| p99 latency | 164.3 ms | 138.7 ms | 243.8 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.38 blocks | 0.42 blocks | no cohort |
| Rate limited | 29 | 76 | 6 |
| Unsupported | 0 | 0 | 238 |
| Samples | 8,092 | 8,166 | 8,218 |
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
+6.4points
- Latency+6.4
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +6.4, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+34.7points
- Availability+29.7
- Head freshness*+9.5
- Latency−2.4
- Correctness−2.2
The parts add to +34.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.