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.2 days observed · generated 2026-08-27 01:38:36 UTC
| Metric | Tenderly | 1RPC | Cloudflare |
|---|---|---|---|
| Rank | 3 | 8 | 9 |
| Score | 93.6 | 62.6 | 56.1 |
| Status | Excellent | Degraded | Degraded |
| Availability | 99.96% | 85.50% | 23.10% |
| p50 latency | 19.9 ms | 225.7 ms | 15.3 ms |
| p95 latency | 73.0 ms | 4391.3 ms | 89.5 ms |
| p99 latency | 880.2 ms | 7602.5 ms | 254.7 ms |
| Correctness | 99.99% | 97.48% | 100.00% |
| Head lag | 0.51 blocks | 0.91 blocks | no cohort |
| Rate limited | 0 | 14,719 | 77 |
| Unsupported | 0 | 0 | 2,523 |
| Samples | 85,845 | 18,270 | 85,644 |
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
+31.0points
- Latency+24.2
- Availability+5.8
- Correctness+0.5
- Head freshness+0.5
The parts add to +31.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+37.5points
- Availability+29.7
- Head freshness*+9.4
- Correctness−2.2
- Latency+0.6
The parts add to +37.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.