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 12:59:40 UTC
| Metric | PublicNode | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 2 | 6 | 9 |
| Score | 99.0 | 77.8 | 53.0 |
| Status | Excellent | Good | Degraded |
| Availability | 99.97% | 100.00% | 23.15% |
| p50 latency | 19.3 ms | 107.1 ms | 15.3 ms |
| p95 latency | 36.8 ms | 194.3 ms | 88.1 ms |
| p99 latency | 83.1 ms | 235.0 ms | 189.7 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.51 blocks | no cohort |
| Rate limited | 0 | 6,201 | 55 |
| Unsupported | 0 | 73 | 1,141 |
| Samples | 39,188 | 8,913 | 38,821 |
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.2points
- Latency+21.2
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +21.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+45.9points
- Availability+29.7
- Head freshness*+9.4
- Latency+9.0
- Correctness−2.2
The parts add to +45.9, 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.