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
30d window · 2.4 days observed · generated 2026-08-27 06:54:24 UTC
| Metric | dRPC | Merkle | MEV Blocker | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 6 | 7 | 8 |
| Score | 92.9 | 78.8 | 77.9 | 62.5 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.93% | 99.98% | 99.89% | 85.27% |
| p50 latency | 33.8 ms | 106.5 ms | 118.5 ms | 225.7 ms |
| p95 latency | 71.7 ms | 195.5 ms | 209.2 ms | 4391.3 ms |
| p99 latency | 167.3 ms | 243.2 ms | 232.7 ms | 7602.5 ms |
| Correctness | 99.99% | 100.00% | 99.99% | 97.48% |
| Head lag | 0.36 blocks | 0.47 blocks | 0.40 blocks | 0.91 blocks |
| Rate limited | 591 | 15,157 | 2 | 16,188 |
| Unsupported | 0 | 183 | 0 | 0 |
| Samples | 92,805 | 21,793 | 94,196 | 19,953 |
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 dRPC, the highest scorer of those selected.
dRPCvsMerkle
+14.2points
- Latency+14.0
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +14.2, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMEV Blocker
+15.0points
- Latency+15.0
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +15.0, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+30.4points
- Latency+23.4
- Availability+5.9
- Head freshness+0.6
- Correctness+0.5
The parts add to +30.4, exactly — the score is a weighted sum, so it comes apart.