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 07:14:28 UTC
| Metric | Tenderly | Cloudflare |
|---|---|---|
| Rank | 2 | 8 |
| Score | 98.5 | 51.2 |
| Status | Excellent | Degraded |
| Availability | 100.00% | 23.12% |
| p50 latency | 18.5 ms | 12.9 ms |
| p95 latency | 32.0 ms | 69.4 ms |
| p99 latency | 65.0 ms | 130.6 ms |
| Correctness | 100.00% | 100.00% |
| Head lag | 0.48 blocks | no cohort |
| Rate limited | 0 | 0 |
| Unsupported | 0 | 252 |
| Samples | 8,479 | 8,497 |
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.
TenderlyvsCloudflare
+47.3points
- Availability+29.7
- Latency+10.3
- Head freshness*+9.4
- Correctness−2.2
The parts add to +47.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.