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
7d window · 2.5 days observed · generated 2026-08-27 07:59:54 UTC
| Metric | Tenderly | dRPC | Cloudflare |
|---|---|---|---|
| Rank | 2 | 3 | 9 |
| Score | 95.1 | 92.8 | 55.3 |
| Status | Excellent | Excellent | Degraded |
| Availability | 99.97% | 99.93% | 23.10% |
| p50 latency | 19.8 ms | 33.8 ms | 15.0 ms |
| p95 latency | 60.1 ms | 71.8 ms | 87.1 ms |
| p99 latency | 821.0 ms | 167.0 ms | 252.5 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.50 blocks | 0.36 blocks | no cohort |
| Rate limited | 0 | 599 | 77 |
| Unsupported | 0 | 0 | 2,827 |
| Samples | 96,132 | 94,542 | 95,944 |
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
+2.3points
- Latency+2.5
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +2.3, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+39.8points
- Availability+29.7
- Head freshness*+9.4
- Latency+2.9
- Correctness−2.2
The parts add to +39.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.