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 08:00:31 UTC
| Metric | Merkle | 1RPC | Cloudflare |
|---|---|---|---|
| Rank | 6 | 8 | 9 |
| Score | 78.0 | 59.0 | 53.4 |
| Status | Good | Degraded | Degraded |
| Availability | 100.00% | 76.74% | 23.12% |
| p50 latency | 107.3 ms | 1326.0 ms | 14.7 ms |
| p95 latency | 192.5 ms | 7406.7 ms | 86.7 ms |
| p99 latency | 256.1 ms | 9776.0 ms | 216.5 ms |
| Correctness | 100.00% | 96.96% | 100.00% |
| Head lag | 0.52 blocks | 0.94 blocks | no cohort |
| Rate limited | 5,979 | 6,393 | 27 |
| Unsupported | 76 | 0 | 1,089 |
| Samples | 8,779 | 7,677 | 37,295 |
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.0points
- Availability+9.3
- Latency+8.6
- Correctness+0.6
- Head freshness+0.5
The parts add to +19.0, exactly — the score is a weighted sum, so it comes apart.
MerklevsCloudflare
+24.6points
- Availability+29.7
- Latency−12.3
- Head freshness*+9.4
- Correctness−2.2
The parts add to +24.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.