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 23:29:54 UTC
| Metric | Tenderly | 1RPC | Cloudflare |
|---|---|---|---|
| Rank | 2 | 8 | 9 |
| Score | 98.9 | 64.1 | 52.4 |
| Status | Excellent | Degraded | Degraded |
| Availability | 99.97% | 89.01% | 23.10% |
| p50 latency | 19.8 ms | 259.6 ms | 16.1 ms |
| p95 latency | 37.4 ms | 2579.7 ms | 93.8 ms |
| p99 latency | 253.7 ms | 4625.5 ms | 247.8 ms |
| Correctness | 99.99% | 98.18% | 100.00% |
| Head lag | 0.49 blocks | 0.94 blocks | no cohort |
| Rate limited | 0 | 6,524 | 39 |
| Unsupported | 0 | 0 | 1,124 |
| Samples | 38,080 | 7,814 | 37,994 |
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.
Tenderlyvs1RPC
+34.7points
- Latency+29.5
- Availability+4.4
- Head freshness+0.5
- Correctness+0.4
The parts add to +34.7, 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.