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
30d window · 2.7 days observed · generated 2026-08-27 13:41:02 UTC
| Metric | 1RPC | Cloudflare |
|---|---|---|
| Rank | 8 | 9 |
| Score | 62.4 | 54.8 |
| Status | Degraded | Degraded |
| Availability | 84.99% | 23.11% |
| p50 latency | 225.7 ms | 15.1 ms |
| p95 latency | 4391.3 ms | 87.6 ms |
| p99 latency | 7602.5 ms | 250.7 ms |
| Correctness | 97.48% | 100.00% |
| Head lag | 0.91 blocks | no cohort |
| Rate limited | 18,082 | 96 |
| Unsupported | 0 | 3,097 |
| Samples | 22,126 | 105,172 |
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 1RPC, the highest scorer of those selected.
1RPCvsCloudflare
+7.6points
- Availability+23.7
- Latency−22.3
- Head freshness*+8.9
- Correctness−2.7
The parts add to +7.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.