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-27 08:51:24 UTC
| Metric | Tenderly | NodeReal | Cloudflare |
|---|---|---|---|
| Rank | 1 | 4 | 9 |
| Score | 99.4 | 86.4 | 52.6 |
| Status | Excellent | Good | Degraded |
| Availability | 99.97% | 100.00% | 23.13% |
| p50 latency | 19.4 ms | 87.2 ms | 15.7 ms |
| p95 latency | 35.3 ms | 100.2 ms | 90.3 ms |
| p99 latency | 130.9 ms | 128.5 ms | 241.8 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.34 blocks | no cohort |
| Rate limited | 0 | 0 | 43 |
| Unsupported | 0 | 0 | 1,139 |
| Samples | 38,604 | 38,028 | 38,585 |
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
+13.0points
- Latency+13.2
- Head freshness−0.2
- Availability−0.0
- Correctness−0.0
The parts add to +13.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+46.7points
- Availability+29.7
- Latency+9.9
- Head freshness*+9.4
- Correctness−2.2
The parts add to +46.7, 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.