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-26 14:55:44 UTC
| Metric | PublicNode | Tenderly | Cloudflare |
|---|---|---|---|
| Rank | 1 | 3 | 9 |
| Score | 99.4 | 93.1 | 55.6 |
| Status | Excellent | Excellent | Degraded |
| Availability | 99.97% | 99.95% | 23.09% |
| p50 latency | 19.2 ms | 20.4 ms | 15.8 ms |
| p95 latency | 32.4 ms | 73.4 ms | 90.0 ms |
| p99 latency | 71.6 ms | 892.3 ms | 253.6 ms |
| Correctness | 99.98% | 99.97% | 100.00% |
| Head lag | 0.49 blocks | 0.51 blocks | no cohort |
| Rate limited | 0 | 0 | 9 |
| Unsupported | 0 | 0 | 1,145 |
| Samples | 39,073 | 38,830 | 38,782 |
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
+6.3points
- Latency+6.3
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +6.3, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+43.8points
- Availability+29.7
- Head freshness*+9.4
- Latency+6.9
- Correctness−2.2
The parts add to +43.8, 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.