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.4 days observed · generated 2026-08-28 06:50:38 UTC
| Metric | NodeReal | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 4 | 6 | 9 |
| Score | 87.0 | 78.2 | 53.9 |
| Status | Good | Good | Degraded |
| Availability | 99.83% | 99.99% | 23.11% |
| p50 latency | 87.4 ms | 106.7 ms | 14.9 ms |
| p95 latency | 100.1 ms | 195.0 ms | 87.2 ms |
| p99 latency | 128.7 ms | 245.1 ms | 250.9 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.34 blocks | 0.49 blocks | no cohort |
| Rate limited | 0 | 21,395 | 111 |
| Unsupported | 0 | 262 | 3,914 |
| Samples | 130,895 | 30,946 | 132,991 |
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
+8.8points
- Latency+8.7
- Head freshness+0.2
- Availability−0.1
- Correctness−0.0
The parts add to +8.8, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsCloudflare
+33.1points
- Availability+29.7
- Head freshness*+9.6
- Latency−3.9
- Correctness−2.2
The parts add to +33.1, 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.