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 23:11:29 UTC
| Metric | Tenderly | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 1 | 6 | 9 |
| Score | 99.4 | 78.0 | 53.4 |
| Status | Excellent | Good | Degraded |
| Availability | 99.98% | 100.00% | 23.13% |
| p50 latency | 19.2 ms | 107.4 ms | 15.1 ms |
| p95 latency | 33.0 ms | 192.4 ms | 87.2 ms |
| p99 latency | 71.5 ms | 235.0 ms | 247.8 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.54 blocks | no cohort |
| Rate limited | 0 | 5,993 | 40 |
| Unsupported | 0 | 72 | 1,103 |
| Samples | 37,565 | 8,749 | 37,593 |
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.4points
- Latency+21.4
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +21.4, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+46.0points
- Availability+29.7
- Head freshness*+9.4
- Latency+9.1
- Correctness−2.2
The parts add to +46.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.