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
- dRPC
- Tenderly
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
30d window · 2.1 days observed · generated 2026-08-26 23:44:38 UTC
| Metric | Tenderly | Merkle | MEV Blocker | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 6 | 7 | 8 |
| Score | 92.0 | 78.9 | 77.9 | 63.8 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.96% | 99.98% | 99.88% | 88.36% |
| p50 latency | 20.0 ms | 106.7 ms | 118.5 ms | 189.3 ms |
| p95 latency | 80.6 ms | 196.1 ms | 209.4 ms | 2922.0 ms |
| p99 latency | 900.5 ms | 243.2 ms | 233.5 ms | 6561.8 ms |
| Correctness | 99.99% | 100.00% | 99.99% | 97.72% |
| Head lag | 0.51 blocks | 0.47 blocks | 0.40 blocks | 0.90 blocks |
| Rate limited | 0 | 13,342 | 1 | 14,222 |
| Unsupported | 0 | 161 | 0 | 0 |
| Samples | 82,782 | 19,213 | 82,626 | 17,341 |
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 Tenderly, the highest scorer of those selected.
TenderlyvsMerkle
+13.2points
- Latency+13.2
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +13.2, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMEV Blocker
+14.1points
- Latency+14.2
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +14.1, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+28.2points
- Latency+22.7
- Availability+4.6
- Correctness+0.5
- Head freshness+0.4
The parts add to +28.2, exactly — the score is a weighted sum, so it comes apart.