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
7d window · 2.6 days observed · generated 2026-08-27 11:27:22 UTC
| Metric | PublicNode | Tenderly | Cloudflare |
|---|---|---|---|
| Rank | 1 | 2 | 9 |
| Score | 99.4 | 95.6 | 55.1 |
| Status | Excellent | Excellent | Degraded |
| Availability | 99.97% | 99.96% | 23.11% |
| p50 latency | 18.5 ms | 19.8 ms | 15.0 ms |
| p95 latency | 33.8 ms | 56.8 ms | 86.7 ms |
| p99 latency | 71.8 ms | 801.0 ms | 251.1 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.50 blocks | no cohort |
| Rate limited | 0 | 0 | 96 |
| Unsupported | 0 | 0 | 2,991 |
| Samples | 102,513 | 101,731 | 101,558 |
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
+3.8points
- Latency+3.8
- Head freshness+0.0
- Availability+0.0
- Correctness−0.0
The parts add to +3.8, 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.