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 09:18:22 UTC
| Metric | Tenderly | dRPC | Cloudflare |
|---|---|---|---|
| Rank | 2 | 3 | 8 |
| Score | 99.1 | 88.3 | 50.4 |
| Status | Excellent | Good | Degraded |
| Availability | 99.98% | 99.93% | 23.06% |
| p50 latency | 18.5 ms | 31.4 ms | 13.3 ms |
| p95 latency | 32.7 ms | 64.2 ms | 75.5 ms |
| p99 latency | 105.1 ms | 159.2 ms | 116.8 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.48 blocks | 0.36 blocks | no cohort |
| Rate limited | 0 | 39 | 7 |
| Unsupported | 0 | 0 | 256 |
| Samples | 8,582 | 8,445 | 8,598 |
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.
TenderlyvsdRPC
+10.8points
- Latency+10.9
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +10.8, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+48.7points
- Availability+29.7
- Latency+11.8
- Head freshness*+9.4
- Correctness−2.2
The parts add to +48.7, 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.