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.1 days observed · generated 2026-08-27 23:46:00 UTC
| Metric | NodeReal | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 4 | 5 | 9 |
| Score | 87.3 | 84.6 | 54.0 |
| Status | Good | Good | Degraded |
| Availability | 99.84% | 99.98% | 23.11% |
| p50 latency | 87.4 ms | 105.2 ms | 15.3 ms |
| p95 latency | 99.9 ms | 122.7 ms | 88.8 ms |
| p99 latency | 125.3 ms | 148.2 ms | 253.4 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.34 blocks | 0.42 blocks | no cohort |
| Rate limited | 0 | 1,237 | 111 |
| Unsupported | 0 | 0 | 3,577 |
| Samples | 119,636 | 121,104 | 121,499 |
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.
NodeRealvsBlast API
+2.8points
- Latency+2.7
- Head freshness+0.1
- Availability−0.1
- Correctness+0.0
The parts add to +2.8, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsCloudflare
+33.3points
- Availability+29.7
- Head freshness*+9.6
- Latency−3.7
- Correctness−2.2
The parts add to +33.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.