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 · 3.0 days observed · generated 2026-08-27 20:24:40 UTC
| Metric | Tenderly | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 2 | 6 | 9 |
| Score | 97.1 | 78.4 | 54.1 |
| Status | Excellent | Good | Degraded |
| Availability | 99.97% | 99.98% | 23.11% |
| p50 latency | 19.8 ms | 107.0 ms | 15.3 ms |
| p95 latency | 48.6 ms | 195.2 ms | 89.6 ms |
| p99 latency | 721.5 ms | 241.4 ms | 253.1 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.50 blocks | 0.49 blocks | no cohort |
| Rate limited | 0 | 18,663 | 96 |
| Unsupported | 0 | 227 | 3,419 |
| Samples | 116,246 | 26,954 | 116,076 |
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
+18.7points
- Latency+18.7
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +18.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+43.0points
- Availability+29.7
- Head freshness*+9.4
- Latency+6.1
- Correctness−2.2
The parts add to +43.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.