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
7d window · 2.7 days observed · generated 2026-08-27 13:17:09 UTC
| Metric | dRPC | 1RPC | Cloudflare |
|---|---|---|---|
| Rank | 3 | 8 | 9 |
| Score | 92.3 | 62.4 | 54.9 |
| Status | Excellent | Degraded | Degraded |
| Availability | 99.93% | 84.99% | 23.11% |
| p50 latency | 33.8 ms | 225.7 ms | 15.0 ms |
| p95 latency | 72.0 ms | 4391.3 ms | 87.4 ms |
| p99 latency | 168.5 ms | 7602.5 ms | 250.5 ms |
| Correctness | 99.99% | 97.48% | 100.00% |
| Head lag | 0.36 blocks | 0.91 blocks | no cohort |
| Rate limited | 639 | 17,970 | 96 |
| Unsupported | 0 | 0 | 3,077 |
| Samples | 102,977 | 21,996 | 104,527 |
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
+29.9points
- Latency+22.8
- Availability+6.0
- Head freshness+0.6
- Correctness+0.5
The parts add to +29.9, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+37.4points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency+0.4
The parts add to +37.4, 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.