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
1h window · 60 minutes observed · generated 2026-08-28 00:03:28 UTC
| Metric | PublicNode | Tenderly | Cloudflare |
|---|---|---|---|
| Rank | 1 | 2 | 8 |
| Score | 99.4 | 98.9 | 55.2 |
| Status | Excellent | Excellent | Degraded |
| Availability | 100.00% | 100.00% | 23.20% |
| p50 latency | 17.7 ms | 17.9 ms | 12.6 ms |
| p95 latency | 29.3 ms | 31.4 ms | 68.8 ms |
| p99 latency | 52.3 ms | 51.8 ms | 130.8 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.48 blocks | no cohort |
| Rate limited | 0 | 0 | 0 |
| Unsupported | 0 | 0 | 46 |
| Samples | 1,619 | 1,611 | 1,595 |
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 PublicNode, the highest scorer of those selected.
PublicNodevsTenderly
+0.5points
- Latency+0.5
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +0.5, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+44.3points
- Availability+29.7
- Head freshness*+9.4
- Latency+7.4
- Correctness−2.2
The parts add to +44.3, 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.