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 00:41:59 UTC
| Metric | Merkle | 1RPC | Cloudflare |
|---|---|---|---|
| Rank | 6 | 8 | 9 |
| Score | 78.0 | 58.5 | 52.4 |
| Status | Good | Degraded | Degraded |
| Availability | 100.00% | 75.73% | 23.11% |
| p50 latency | 106.9 ms | 2024.4 ms | 16.2 ms |
| p95 latency | 195.7 ms | 6590.4 ms | 93.3 ms |
| p99 latency | 239.8 ms | 9196.2 ms | 247.3 ms |
| Correctness | 100.00% | 96.63% | 100.00% |
| Head lag | 0.47 blocks | 0.95 blocks | no cohort |
| Rate limited | 6,169 | 6,584 | 45 |
| Unsupported | 80 | 0 | 1,133 |
| Samples | 8,886 | 7,900 | 38,332 |
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 Merkle, the highest scorer of those selected.
Merklevs1RPC
+19.5points
- Availability+9.7
- Latency+8.6
- Correctness+0.7
- Head freshness+0.6
The parts add to +19.5, exactly — the score is a weighted sum, so it comes apart.
MerklevsCloudflare
+25.6points
- Availability+29.7
- Latency−11.3
- Head freshness*+9.4
- Correctness−2.2
The parts add to +25.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.