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:45:12 UTC
| Metric | NodeReal | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 4 | 5 | 8 |
| Score | 82.2 | 78.3 | 48.9 |
| Status | Good | Good | Poor |
| Availability | 99.97% | 99.92% | 23.10% |
| p50 latency | 87.1 ms | 106.4 ms | 15.4 ms |
| p95 latency | 99.0 ms | 123.9 ms | 87.4 ms |
| p99 latency | 117.5 ms | 151.6 ms | 267.1 ms |
| Correctness | 99.97% | 100.00% | 100.00% |
| Head lag | 0.34 blocks | 0.41 blocks | no cohort |
| Rate limited | 0 | 44 | 15 |
| Unsupported | 0 | 0 | 271 |
| Samples | 9,163 | 9,313 | 9,312 |
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
+3.9points
- Latency+3.8
- Head freshness+0.1
- Availability+0.0
- Correctness−0.0
The parts add to +3.9, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsCloudflare
+33.3points
- Availability+29.7
- Head freshness*+9.6
- Latency−3.8
- 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.