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 · 4.4 days observed · generated 2026-08-29 05:12:56 UTC
| Metric | 1RPC | Cloudflare |
|---|---|---|
| Rank | 8 | 9 |
| Score | 61.7 | 53.6 |
| Status | Degraded | Degraded |
| Availability | 83.07% | 23.12% |
| p50 latency | 320.2 ms | 14.6 ms |
| p95 latency | 4778.7 ms | 86.6 ms |
| p99 latency | 8408.8 ms | 248.4 ms |
| Correctness | 97.52% | 100.00% |
| Head lag | 0.90 blocks | no cohort |
| Rate limited | 29,061 | 122 |
| Unsupported | 0 | 4,984 |
| Samples | 35,390 | 169,276 |
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
+8.1points
- Availability+23.0
- Latency−21.1
- Head freshness*+8.9
- Correctness−2.7
The parts add to +8.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.