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
1h window · 60 minutes observed · generated 2026-08-27 00:43:05 UTC
| Metric | Tenderly | dRPC | Cloudflare |
|---|---|---|---|
| Rank | 1 | 3 | 9 |
| Score | 99.4 | 90.8 | 55.6 |
| Status | Excellent | Excellent | Degraded |
| Availability | 100.00% | 99.94% | 23.28% |
| p50 latency | 18.6 ms | 33.7 ms | 11.4 ms |
| p95 latency | 31.0 ms | 66.9 ms | 69.8 ms |
| p99 latency | 65.4 ms | 159.7 ms | 134.1 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.37 blocks | no cohort |
| Rate limited | 0 | 4 | 6 |
| Unsupported | 0 | 0 | 46 |
| Samples | 1,586 | 1,576 | 1,602 |
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
+8.6points
- Latency+8.8
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+43.8points
- Availability+29.7
- Head freshness*+9.4
- Latency+7.0
- Correctness−2.2
The parts add to +43.8, 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.