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-26 22:14:26 UTC
| Metric | Merkle | 1RPC | Cloudflare |
|---|---|---|---|
| Rank | 6 | 8 | 9 |
| Score | 78.0 | 64.3 | 52.3 |
| Status | Good | Degraded | Degraded |
| Availability | 100.00% | 89.50% | 23.09% |
| p50 latency | 107.1 ms | 259.6 ms | 16.1 ms |
| p95 latency | 196.8 ms | 2579.7 ms | 94.1 ms |
| p99 latency | 241.2 ms | 4625.5 ms | 247.6 ms |
| Correctness | 100.00% | 98.18% | 100.00% |
| Head lag | 0.46 blocks | 0.94 blocks | no cohort |
| Rate limited | 6,064 | 6,453 | 39 |
| Unsupported | 79 | 0 | 1,113 |
| Samples | 8,753 | 7,733 | 37,567 |
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
+13.7points
- Latency+8.6
- Availability+4.2
- Head freshness+0.6
- Correctness+0.4
The parts add to +13.7, exactly — the score is a weighted sum, so it comes apart.
MerklevsCloudflare
+25.7points
- Availability+29.7
- Latency−11.3
- Head freshness*+9.4
- Correctness−2.2
The parts add to +25.7, 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.