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.2 days observed · generated 2026-08-27 01:54:53 UTC
| Metric | Tenderly | Merkle | MEV Blocker | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 6 | 7 | 8 |
| Score | 93.8 | 79.2 | 78.2 | 62.6 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.96% | 99.98% | 99.88% | 85.50% |
| p50 latency | 19.9 ms | 106.6 ms | 118.5 ms | 225.7 ms |
| p95 latency | 71.9 ms | 195.9 ms | 209.5 ms | 4391.3 ms |
| p99 latency | 877.9 ms | 243.1 ms | 233.4 ms | 7602.5 ms |
| Correctness | 99.99% | 100.00% | 99.99% | 97.48% |
| Head lag | 0.51 blocks | 0.46 blocks | 0.40 blocks | 0.91 blocks |
| Rate limited | 0 | 13,899 | 2 | 14,793 |
| Unsupported | 0 | 170 | 0 | 0 |
| Samples | 86,292 | 20,012 | 86,130 | 18,354 |
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
+14.6points
- Latency+14.7
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +14.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMEV Blocker
+15.5points
- Latency+15.6
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +15.5, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+31.1points
- Latency+24.4
- Availability+5.8
- Correctness+0.5
- Head freshness+0.5
The parts add to +31.1, exactly — the score is a weighted sum, so it comes apart.