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
1h window · 60 minutes observed · generated 2026-08-29 00:52:04 UTC
| Metric | PublicNode | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 1 | 7 | 9 |
| Score | 99.4 | 72.8 | 53.3 |
| Status | Excellent | Degraded | Degraded |
| Availability | 100.00% | 100.00% | 23.17% |
| p50 latency | 19.5 ms | 118.6 ms | 11.3 ms |
| p95 latency | 29.0 ms | 205.4 ms | 67.8 ms |
| p99 latency | 44.6 ms | 221.7 ms | 236.1 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.37 blocks | no cohort |
| Rate limited | 0 | 0 | 0 |
| Unsupported | 0 | 0 | 45 |
| Samples | 1,606 | 1,594 | 1,597 |
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
+26.6points
- Latency+26.8
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +26.6, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+46.2points
- Availability+29.7
- Head freshness*+9.4
- Latency+9.3
- Correctness−2.2
The parts add to +46.2, 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.