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 14:53:45 UTC
| Metric | Tenderly | dRPC | Cloudflare |
|---|---|---|---|
| Rank | 1 | 3 | 8 |
| Score | 99.4 | 88.1 | 48.1 |
| Status | Excellent | Good | Poor |
| Availability | 99.95% | 99.95% | 23.19% |
| p50 latency | 20.2 ms | 34.2 ms | 16.5 ms |
| p95 latency | 34.5 ms | 74.4 ms | 95.8 ms |
| p99 latency | 77.8 ms | 185.6 ms | 155.2 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.36 blocks | no cohort |
| Rate limited | 0 | 40 | 12 |
| Unsupported | 0 | 0 | 277 |
| Samples | 9,562 | 9,397 | 9,559 |
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
+11.3points
- Latency+11.4
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +11.3, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+51.3points
- Availability+29.7
- Latency+14.4
- Head freshness*+9.4
- Correctness−2.2
The parts add to +51.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.