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-28 16:07:01 UTC
| Metric | PublicNode | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 2 | 6 | 9 |
| Score | 98.5 | 77.4 | 53.0 |
| Status | Excellent | Good | Degraded |
| Availability | 99.98% | 100.00% | 23.12% |
| p50 latency | 21.2 ms | 107.4 ms | 13.5 ms |
| p95 latency | 36.6 ms | 196.2 ms | 85.6 ms |
| p99 latency | 77.5 ms | 265.9 ms | 153.3 ms |
| Correctness | 99.98% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.53 blocks | no cohort |
| Rate limited | 0 | 6,026 | 21 |
| Unsupported | 0 | 70 | 1,101 |
| Samples | 37,806 | 8,733 | 37,476 |
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.1points
- Latency+21.0
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +21.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+45.5points
- Availability+29.7
- Head freshness*+9.4
- Latency+8.6
- Correctness−2.2
The parts add to +45.5, 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.