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
7d window · 3.0 days observed · generated 2026-08-27 21:02:47 UTC
| Metric | PublicNode | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 1 | 6 | 9 |
| Score | 99.4 | 78.4 | 54.1 |
| Status | Excellent | Good | Degraded |
| Availability | 99.98% | 99.98% | 23.11% |
| p50 latency | 19.4 ms | 107.0 ms | 15.4 ms |
| p95 latency | 36.0 ms | 195.1 ms | 89.5 ms |
| p99 latency | 78.3 ms | 242.0 ms | 253.6 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.49 blocks | no cohort |
| Rate limited | 0 | 18,838 | 96 |
| Unsupported | 0 | 227 | 3,451 |
| Samples | 118,200 | 27,220 | 117,100 |
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.0points
- Latency+21.0
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +21.0, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+45.3points
- Availability+29.7
- Head freshness*+9.4
- Latency+8.4
- Correctness−2.2
The parts add to +45.3, 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.