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
- Tenderly
- PublicNode
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
24h window · 24 hours observed · generated 2026-08-27 13:40:46 UTC
| Metric | PublicNode | 1RPC | Cloudflare |
|---|---|---|---|
| Rank | 2 | 8 | 9 |
| Score | 98.8 | 57.8 | 53.1 |
| Status | Excellent | Degraded | Degraded |
| Availability | 99.97% | 73.97% | 23.14% |
| p50 latency | 19.4 ms | 2024.4 ms | 15.1 ms |
| p95 latency | 37.3 ms | 6590.4 ms | 88.0 ms |
| p99 latency | 86.7 ms | 9196.2 ms | 217.1 ms |
| Correctness | 100.00% | 96.63% | 100.00% |
| Head lag | 0.49 blocks | 0.95 blocks | no cohort |
| Rate limited | 0 | 6,577 | 55 |
| Unsupported | 0 | 0 | 1,126 |
| Samples | 38,682 | 7,899 | 38,308 |
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
+41.0points
- Latency+29.4
- Availability+10.4
- Correctness+0.7
- Head freshness+0.5
The parts add to +41.0, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+45.7points
- Availability+29.7
- Head freshness*+9.4
- Latency+8.9
- Correctness−2.2
The parts add to +45.7, 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.