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 02:15:34 UTC
| Metric | Tenderly | PublicNode | Cloudflare |
|---|---|---|---|
| Rank | 1 | 2 | 9 |
| Score | 99.4 | 98.7 | 55.3 |
| Status | Excellent | Excellent | Degraded |
| Availability | 100.00% | 99.99% | 23.19% |
| p50 latency | 19.0 ms | 17.1 ms | 12.8 ms |
| p95 latency | 32.3 ms | 35.4 ms | 72.3 ms |
| p99 latency | 70.7 ms | 93.2 ms | 260.9 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.49 blocks | no cohort |
| Rate limited | 0 | 0 | 6 |
| Unsupported | 0 | 0 | 247 |
| Samples | 8,499 | 8,596 | 8,521 |
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.7points
- Latency+0.7
- Availability+0.0
- Head freshness+0.0
- Correctness+0.0
The parts add to +0.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsCloudflare
+44.1points
- Availability+29.7
- Head freshness*+9.4
- Latency+7.2
- Correctness−2.2
The parts add to +44.1, 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.