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 19:55:54 UTC
| Metric | Tenderly | dRPC | Cloudflare |
|---|---|---|---|
| Rank | 1 | 3 | 8 |
| Score | 99.4 | 89.4 | 46.7 |
| Status | Excellent | Good | Poor |
| Availability | 100.00% | 100.00% | 23.10% |
| p50 latency | 17.8 ms | 35.6 ms | 17.5 ms |
| p95 latency | 31.9 ms | 68.6 ms | 99.0 ms |
| p99 latency | 56.8 ms | 185.8 ms | 277.2 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.50 blocks | 0.33 blocks | no cohort |
| Rate limited | 0 | 1 | 0 |
| Unsupported | 0 | 0 | 48 |
| Samples | 1,606 | 1,591 | 1,614 |
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.0points
- Latency+10.2
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +10.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+52.7points
- Availability+29.7
- Latency+15.8
- Head freshness*+9.4
- Correctness−2.2
The parts add to +52.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.