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
- Tenderly
- PublicNode
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
24h window · 24 hours observed · generated 2026-08-28 00:24:15 UTC
| Metric | 1RPC | Cloudflare |
|---|---|---|
| Rank | 8 | 9 |
| Score | 58.4 | 53.5 |
| Status | Degraded | Degraded |
| Availability | 74.93% | 23.14% |
| p50 latency | 1332.6 ms | 15.0 ms |
| p95 latency | 7705.9 ms | 86.8 ms |
| p99 latency | 9776.0 ms | 244.1 ms |
| Correctness | 97.72% | 100.00% |
| Head lag | 0.92 blocks | no cohort |
| Rate limited | 6,443 | 34 |
| Unsupported | 0 | 1,116 |
| Samples | 7,714 | 37,934 |
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
+5.0points
- Latency−21.0
- Availability+19.7
- Head freshness*+8.9
- Correctness−2.7
The parts add to +5.0, 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.