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-28 18:23:09 UTC
| Metric | NodeReal | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 4 | 7 | 8 |
| Score | 82.3 | 69.5 | 47.7 |
| Status | Good | Degraded | Poor |
| Availability | 100.00% | 99.87% | 23.15% |
| p50 latency | 87.1 ms | 123.5 ms | 14.4 ms |
| p95 latency | 99.2 ms | 210.0 ms | 93.9 ms |
| p99 latency | 119.7 ms | 227.6 ms | 167.6 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.36 blocks | 0.39 blocks | no cohort |
| Rate limited | 0 | 0 | 0 |
| Unsupported | 0 | 0 | 259 |
| Samples | 8,566 | 8,731 | 8,743 |
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.8points
- Latency+12.7
- Availability+0.1
- Head freshness+0.0
- Correctness+0.0
The parts add to +12.8, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsCloudflare
+34.6points
- Availability+29.7
- Head freshness*+9.6
- Latency−2.5
- Correctness−2.2
The parts add to +34.6, 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.