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-28 01:07:29 UTC
| Metric | Tenderly | PublicNode | Cloudflare |
|---|---|---|---|
| Rank | 1 | 2 | 9 |
| Score | 99.4 | 98.6 | 54.8 |
| Status | Excellent | Excellent | Degraded |
| Availability | 100.00% | 99.99% | 23.01% |
| p50 latency | 18.5 ms | 19.9 ms | 13.8 ms |
| p95 latency | 31.7 ms | 35.5 ms | 74.9 ms |
| p99 latency | 53.3 ms | 77.5 ms | 251.2 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.46 blocks | 0.48 blocks | no cohort |
| Rate limited | 0 | 0 | 15 |
| Unsupported | 0 | 0 | 243 |
| Samples | 8,314 | 8,377 | 8,300 |
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.8points
- Latency+0.8
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +0.8, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+44.7points
- Availability+29.8
- Head freshness*+9.4
- Latency+7.7
- Correctness−2.2
The parts add to +44.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.