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
24h window · 24 hours observed · generated 2026-08-27 02:33:38 UTC
| Metric | 1RPC | Cloudflare |
|---|---|---|
| Rank | 8 | 9 |
| Score | 58.5 | 52.3 |
| Status | Degraded | Degraded |
| Availability | 75.73% | 23.11% |
| p50 latency | 2024.4 ms | 16.2 ms |
| p95 latency | 6590.4 ms | 93.4 ms |
| p99 latency | 9196.2 ms | 246.9 ms |
| Correctness | 96.63% | 100.00% |
| Head lag | 0.95 blocks | no cohort |
| Rate limited | 6,546 | 45 |
| Unsupported | 0 | 1,126 |
| Samples | 7,857 | 38,113 |
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
+6.2points
- Availability+20.0
- Latency−19.8
- Head freshness*+8.9
- Correctness−2.9
The parts add to +6.2, 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.