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 · 3.4 days observed · generated 2026-08-28 05:23:49 UTC
| Metric | 1RPC | Cloudflare |
|---|---|---|
| Rank | 8 | 9 |
| Score | 61.8 | 54.0 |
| Status | Degraded | Degraded |
| Availability | 83.57% | 23.11% |
| p50 latency | 265.3 ms | 15.0 ms |
| p95 latency | 4975.4 ms | 87.6 ms |
| p99 latency | 8455.9 ms | 251.3 ms |
| Correctness | 97.38% | 100.00% |
| Head lag | 0.91 blocks | no cohort |
| Rate limited | 22,438 | 111 |
| Unsupported | 0 | 3,845 |
| Samples | 27,465 | 130,644 |
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.9points
- Availability+23.2
- Latency−21.5
- Head freshness*+8.9
- Correctness−2.7
The parts add to +7.9, 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.