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 · 2.7 days observed · generated 2026-08-27 12:59:34 UTC
| Metric | NodeReal | 1RPC | Cloudflare |
|---|---|---|---|
| Rank | 4 | 8 | 9 |
| Score | 87.8 | 62.4 | 54.9 |
| Status | Good | Degraded | Degraded |
| Availability | 99.82% | 84.99% | 23.11% |
| p50 latency | 87.4 ms | 225.7 ms | 15.0 ms |
| p95 latency | 100.0 ms | 4391.3 ms | 87.2 ms |
| p99 latency | 125.8 ms | 7602.5 ms | 250.4 ms |
| Correctness | 99.99% | 97.48% | 100.00% |
| Head lag | 0.35 blocks | 0.91 blocks | no cohort |
| Rate limited | 0 | 17,891 | 96 |
| Unsupported | 0 | 0 | 3,063 |
| Samples | 102,472 | 21,906 | 104,054 |
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.
NodeRealvs1RPC
+25.4points
- Latency+18.3
- Availability+5.9
- Head freshness+0.7
- Correctness+0.5
The parts add to +25.4, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsCloudflare
+32.9points
- Availability+29.7
- Head freshness*+9.6
- Latency−4.1
- Correctness−2.2
The parts add to +32.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.