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
24h window · 24 hours observed · generated 2026-08-26 22:16:47 UTC
| Metric | Tenderly | dRPC | Cloudflare |
|---|---|---|---|
| Rank | 2 | 3 | 9 |
| Score | 98.8 | 91.4 | 52.3 |
| Status | Excellent | Excellent | Degraded |
| Availability | 99.97% | 99.93% | 23.10% |
| p50 latency | 19.8 ms | 34.1 ms | 16.1 ms |
| p95 latency | 37.5 ms | 68.4 ms | 94.1 ms |
| p99 latency | 265.0 ms | 168.0 ms | 247.8 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.37 blocks | no cohort |
| Rate limited | 0 | 122 | 39 |
| Unsupported | 0 | 0 | 1,113 |
| Samples | 37,748 | 37,118 | 37,632 |
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
+7.4points
- Latency+7.6
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +7.4, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+46.5points
- Availability+29.7
- Latency+9.6
- Head freshness*+9.4
- Correctness−2.2
The parts add to +46.5, 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.