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
- NodeReal
- dRPC
- Blast API
- Merkle
- MEV Blocker
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 12:26:26 UTC
| Metric | PublicNode | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 2 | 6 | 7 |
| Score | 99.1 | 69.5 | 69.5 |
| Status | Excellent | Degraded | Degraded |
| Availability | 99.97% | 100.00% | 99.95% |
| p50 latency | 20.8 ms | 107.4 ms | 121.9 ms |
| p95 latency | 33.8 ms | 202.7 ms | 206.3 ms |
| p99 latency | 69.8 ms | 232.6 ms | 224.2 ms |
| Correctness | 99.97% | 100.00% | 99.98% |
| Head lag | 0.50 blocks | 0.58 blocks | 0.41 blocks |
| Rate limited | 0 | 1,408 | 0 |
| Unsupported | 0 | 15 | 0 |
| Samples | 8,890 | 2,020 | 8,806 |
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.
PublicNodevsMerkle
+29.6points
- Latency+29.6
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +29.6, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+29.6points
- Latency+29.7
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +29.6, exactly — the score is a weighted sum, so it comes apart.