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
7d window · 2.6 days observed · generated 2026-08-27 10:51:38 UTC
| Metric | Tenderly | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 2 | 6 | 9 |
| Score | 95.5 | 78.6 | 55.2 |
| Status | Excellent | Good | Degraded |
| Availability | 99.96% | 99.98% | 23.11% |
| p50 latency | 19.8 ms | 106.4 ms | 15.0 ms |
| p95 latency | 57.5 ms | 195.9 ms | 86.8 ms |
| p99 latency | 805.5 ms | 243.2 ms | 251.5 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.50 blocks | 0.48 blocks | no cohort |
| Rate limited | 0 | 16,210 | 96 |
| Unsupported | 0 | 199 | 2,962 |
| Samples | 100,755 | 23,349 | 100,591 |
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
+16.9points
- Latency+16.9
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +16.9, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+40.3points
- Availability+29.7
- Head freshness*+9.4
- Latency+3.4
- Correctness−2.2
The parts add to +40.3, 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.