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 09:12:46 UTC
| Metric | Cloudflare | 1RPC |
|---|---|---|
| Rank | 8 | 9 |
| Score | 50.6 | 0.0 |
| Status | Degraded | Poor |
| Availability | 23.09% | 0.00% |
| p50 latency | 13.3 ms | 0.0 ms |
| p95 latency | 74.6 ms | 0.0 ms |
| p99 latency | 116.8 ms | 0.0 ms |
| Correctness | 100.00% | not measured |
| Head lag | no cohort | no cohort |
| Rate limited | 7 | 1,457 |
| Unsupported | 252 | 0 |
| Samples | 8,453 | 1,669 |
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 Cloudflare, the highest scorer of those selected.
Cloudflarevs1RPC
+50.6points
- Correctness*+22.2
- Latency*+18.1
- Availability+10.3
- Head freshness+0.0
The parts add to +50.6, 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.