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
- 1RPC
- Cloudflare
Side by side
24h window · 24 hours observed · generated 2026-08-27 21:02:59 UTC
| Metric | PublicNode | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 2 | 7 | 9 |
| Score | 97.7 | 76.9 | 53.6 |
| Status | Excellent | Good | Degraded |
| Availability | 99.99% | 99.92% | 23.16% |
| p50 latency | 21.5 ms | 121.4 ms | 15.2 ms |
| p95 latency | 41.8 ms | 213.0 ms | 86.7 ms |
| p99 latency | 101.8 ms | 235.3 ms | 248.7 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.48 blocks | 0.40 blocks | no cohort |
| Rate limited | 0 | 3 | 25 |
| Unsupported | 0 | 0 | 1,100 |
| Samples | 37,659 | 37,280 | 37,360 |
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 PublicNode, the highest scorer of those selected.
PublicNodevsMEV Blocker
+20.8points
- Latency+20.9
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +20.8, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+44.1points
- Availability+29.7
- Head freshness*+9.4
- Latency+7.3
- Correctness−2.2
The parts add to +44.1, 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.