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 18:29:31 UTC
| Metric | dRPC | 1RPC | Cloudflare |
|---|---|---|---|
| Rank | 3 | 8 | 9 |
| Score | 91.1 | 57.8 | 53.5 |
| Status | Excellent | Degraded | Degraded |
| Availability | 99.94% | 73.97% | 23.15% |
| p50 latency | 33.7 ms | 2024.4 ms | 15.1 ms |
| p95 latency | 70.7 ms | 6590.4 ms | 86.7 ms |
| p99 latency | 174.0 ms | 9196.2 ms | 246.3 ms |
| Correctness | 99.99% | 96.63% | 100.00% |
| Head lag | 0.37 blocks | 0.95 blocks | no cohort |
| Rate limited | 137 | 6,533 | 36 |
| Unsupported | 0 | 0 | 1,119 |
| Samples | 37,438 | 7,845 | 38,071 |
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.
dRPCvs1RPC
+33.3points
- Latency+21.5
- Availability+10.4
- Head freshness+0.7
- Correctness+0.7
The parts add to +33.3, 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.