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
6h window · 6.0 hours observed · generated 2026-08-27 01:50:44 UTC
| Metric | Tenderly | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 1 | 6 | 9 |
| Score | 99.4 | 77.6 | 54.1 |
| Status | Excellent | Good | Degraded |
| Availability | 99.99% | 100.00% | 23.21% |
| p50 latency | 19.0 ms | 105.9 ms | 13.6 ms |
| p95 latency | 32.2 ms | 193.5 ms | 78.8 ms |
| p99 latency | 71.9 ms | 220.4 ms | 266.5 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.50 blocks | 0.51 blocks | no cohort |
| Rate limited | 0 | 1,475 | 17 |
| Unsupported | 0 | 17 | 275 |
| Samples | 9,432 | 2,111 | 9,467 |
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.8points
- Latency+21.8
- Head freshness+0.0
- Availability−0.0
- Correctness+0.0
The parts add to +21.8, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+45.2points
- Availability+29.7
- Head freshness*+9.4
- Latency+8.4
- Correctness−2.2
The parts add to +45.2, 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.