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
1h window · 60 minutes observed · generated 2026-08-27 20:39:16 UTC
| Metric | dRPC | Cloudflare | 1RPC |
|---|---|---|---|
| Rank | 3 | 8 | 9 |
| Score | 87.7 | 46.6 | 0.0 |
| Status | Good | Poor | Poor |
| Availability | 99.94% | 23.00% | 0.00% |
| p50 latency | 34.7 ms | 17.8 ms | 0.0 ms |
| p95 latency | 74.2 ms | 100.8 ms | 0.0 ms |
| p99 latency | 195.8 ms | 269.5 ms | 0.0 ms |
| Correctness | 100.00% | 100.00% | not measured |
| Head lag | 0.35 blocks | no cohort | no cohort |
| Rate limited | 7 | 0 | 265 |
| Unsupported | 0 | 46 | 0 |
| Samples | 1,565 | 1,597 | 313 |
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.
dRPCvsCloudflare
+41.1points
- Availability+29.8
- Head freshness*+9.6
- Latency+4.0
- Correctness−2.2
The parts add to +41.1, 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.
dRPCvs1RPC
+87.7points
- Availability+40.0
- Correctness*+20.0
- Latency*+18.2
- Head freshness*+9.6
The parts add to +87.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.