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:03:24 UTC
| Metric | Tenderly | PublicNode | Cloudflare |
|---|---|---|---|
| Rank | 1 | 2 | 9 |
| Score | 99.4 | 99.4 | 52.5 |
| Status | Excellent | Excellent | Degraded |
| Availability | 99.98% | 99.98% | 23.13% |
| p50 latency | 19.4 ms | 18.4 ms | 15.8 ms |
| p95 latency | 35.3 ms | 35.4 ms | 91.3 ms |
| p99 latency | 121.6 ms | 74.0 ms | 242.4 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.48 blocks | no cohort |
| Rate limited | 0 | 0 | 36 |
| Unsupported | 0 | 0 | 1,101 |
| Samples | 37,318 | 37,652 | 37,285 |
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.
TenderlyvsPublicNode
+0.0points
- Latency+0.0
- Head freshness−0.0
- Correctness−0.0
- Availability−0.0
The parts add to +0.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+46.9points
- Availability+29.7
- Latency+10.0
- Head freshness*+9.4
- Correctness−2.2
The parts add to +46.9, 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.