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 13:38:25 UTC
| Metric | dRPC | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 3 | 5 | 9 |
| Score | 90.5 | 83.8 | 53.0 |
| Status | Excellent | Good | Degraded |
| Availability | 99.92% | 99.99% | 23.14% |
| p50 latency | 34.1 ms | 105.7 ms | 15.1 ms |
| p95 latency | 72.2 ms | 122.5 ms | 88.1 ms |
| p99 latency | 171.7 ms | 149.0 ms | 217.9 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.37 blocks | 0.41 blocks | no cohort |
| Rate limited | 158 | 331 | 55 |
| Unsupported | 0 | 0 | 1,124 |
| Samples | 37,673 | 38,068 | 38,246 |
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.7points
- Latency+6.7
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +6.7, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+37.5points
- Availability+29.7
- Head freshness*+9.5
- 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.