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
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-27 23:31:45 UTC
| Metric | NodeReal | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 4 | 6 | 8 |
| Score | 82.3 | 70.8 | 48.8 |
| Status | Good | Degraded | Poor |
| Availability | 99.97% | 100.00% | 23.09% |
| p50 latency | 87.1 ms | 107.8 ms | 15.6 ms |
| p95 latency | 99.0 ms | 190.5 ms | 88.0 ms |
| p99 latency | 117.8 ms | 236.0 ms | 269.5 ms |
| Correctness | 99.97% | 100.00% | 100.00% |
| Head lag | 0.33 blocks | 0.52 blocks | no cohort |
| Rate limited | 0 | 1,430 | 15 |
| Unsupported | 0 | 16 | 260 |
| Samples | 8,804 | 2,145 | 8,950 |
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 NodeReal, the highest scorer of those selected.
NodeRealvsMerkle
+11.4points
- Latency+11.2
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +11.4, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsCloudflare
+33.4points
- Availability+29.7
- Head freshness*+9.6
- Latency−3.7
- Correctness−2.2
The parts add to +33.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.