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 10:47:55 UTC
| Metric | PublicNode | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 2 | 6 | 9 |
| Score | 99.2 | 77.8 | 52.9 |
| Status | Excellent | Good | Degraded |
| Availability | 99.97% | 100.00% | 23.12% |
| p50 latency | 18.9 ms | 107.0 ms | 15.5 ms |
| p95 latency | 36.0 ms | 193.4 ms | 88.9 ms |
| p99 latency | 79.5 ms | 237.9 ms | 230.7 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.51 blocks | no cohort |
| Rate limited | 0 | 6,144 | 55 |
| Unsupported | 0 | 76 | 1,131 |
| Samples | 38,876 | 8,833 | 38,491 |
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.
PublicNodevsMerkle
+21.4points
- Latency+21.4
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +21.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+46.4points
- Availability+29.7
- Latency+9.5
- Head freshness*+9.4
- Correctness−2.2
The parts add to +46.4, 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.