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
- PublicNode
- Tenderly
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
30d window · 2.5 days observed · generated 2026-08-27 07:30:35 UTC
| Metric | PublicNode | 1RPC | Cloudflare |
|---|---|---|---|
| Rank | 1 | 8 | 9 |
| Score | 99.4 | 62.5 | 55.4 |
| Status | Excellent | Degraded | Degraded |
| Availability | 99.97% | 85.27% | 23.10% |
| p50 latency | 18.2 ms | 225.7 ms | 15.0 ms |
| p95 latency | 33.5 ms | 4391.3 ms | 87.1 ms |
| p99 latency | 69.7 ms | 7602.5 ms | 252.7 ms |
| Correctness | 99.99% | 97.48% | 100.00% |
| Head lag | 0.49 blocks | 0.91 blocks | no cohort |
| Rate limited | 0 | 16,359 | 77 |
| Unsupported | 0 | 0 | 2,805 |
| Samples | 96,070 | 20,148 | 95,160 |
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.
PublicNodevs1RPC
+36.9points
- Latency+30.0
- Availability+5.9
- Correctness+0.5
- Head freshness+0.5
The parts add to +36.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+44.0points
- Availability+29.7
- Head freshness*+9.4
- Latency+7.1
- Correctness−2.2
The parts add to +44.0, 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.