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:47:29 UTC
| Metric | Tenderly | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 2 | 6 | 9 |
| Score | 99.0 | 78.0 | 52.4 |
| Status | Excellent | Good | Degraded |
| Availability | 99.98% | 100.00% | 23.11% |
| p50 latency | 19.7 ms | 106.9 ms | 16.1 ms |
| p95 latency | 36.9 ms | 195.9 ms | 93.4 ms |
| p99 latency | 232.7 ms | 239.8 ms | 247.5 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.47 blocks | no cohort |
| Rate limited | 0 | 6,208 | 45 |
| Unsupported | 0 | 80 | 1,138 |
| Samples | 38,533 | 8,933 | 38,478 |
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 Tenderly, the highest scorer of those selected.
TenderlyvsMerkle
+21.0points
- Latency+21.0
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +21.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+46.6points
- Availability+29.7
- Latency+9.7
- Head freshness*+9.4
- Correctness−2.2
The parts add to +46.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.