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
6h window · 6.0 hours observed · generated 2026-08-27 22:02:20 UTC
| Metric | Tenderly | NodeReal | Cloudflare |
|---|---|---|---|
| Rank | 1 | 4 | 8 |
| Score | 99.4 | 82.8 | 47.9 |
| Status | Excellent | Good | Poor |
| Availability | 100.00% | 99.98% | 23.12% |
| p50 latency | 19.0 ms | 87.1 ms | 16.7 ms |
| p95 latency | 32.6 ms | 98.8 ms | 95.2 ms |
| p99 latency | 55.8 ms | 118.3 ms | 273.3 ms |
| Correctness | 100.00% | 99.98% | 100.00% |
| Head lag | 0.47 blocks | 0.33 blocks | no cohort |
| Rate limited | 0 | 0 | 0 |
| Unsupported | 0 | 0 | 241 |
| Samples | 8,159 | 8,031 | 8,149 |
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.
TenderlyvsNodeReal
+16.6points
- Latency+16.8
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +16.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+51.5points
- Availability+29.7
- Latency+14.6
- Head freshness*+9.4
- Correctness−2.2
The parts add to +51.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.