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
1h window · 60 minutes observed · generated 2026-08-28 21:32:39 UTC
| Metric | NodeReal | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 4 | 7 | 8 |
| Score | 81.5 | 69.5 | 49.6 |
| Status | Good | Degraded | Poor |
| Availability | 100.00% | 99.94% | 23.33% |
| p50 latency | 86.9 ms | 122.2 ms | 13.4 ms |
| p95 latency | 99.0 ms | 209.2 ms | 80.2 ms |
| p99 latency | 120.6 ms | 227.0 ms | 267.5 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.34 blocks | 0.39 blocks | no cohort |
| Rate limited | 0 | 0 | 5 |
| Unsupported | 0 | 0 | 47 |
| Samples | 1,579 | 1,602 | 1,610 |
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.
NodeRealvsMEV Blocker
+12.0points
- Latency+11.9
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +12.0, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsCloudflare
+31.9points
- Availability+29.6
- Head freshness*+9.6
- Latency−5.1
- Correctness−2.2
The parts add to +31.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.