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
24h window · 24 hours observed · generated 2026-08-27 01:54:55 UTC
| Metric | dRPC | Merkle | MEV Blocker | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 6 | 7 | 8 |
| Score | 91.1 | 78.0 | 77.1 | 58.5 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.92% | 100.00% | 99.89% | 75.73% |
| p50 latency | 34.1 ms | 107.0 ms | 119.2 ms | 2024.4 ms |
| p95 latency | 69.4 ms | 195.2 ms | 210.7 ms | 6590.4 ms |
| p99 latency | 170.4 ms | 239.8 ms | 233.8 ms | 9196.2 ms |
| Correctness | 99.99% | 100.00% | 99.99% | 96.63% |
| Head lag | 0.38 blocks | 0.46 blocks | 0.39 blocks | 0.95 blocks |
| Rate limited | 128 | 6,224 | 2 | 6,644 |
| Unsupported | 0 | 82 | 0 | 0 |
| Samples | 38,134 | 8,946 | 38,681 | 7,968 |
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
+13.1points
- Latency+13.1
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +13.1, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMEV Blocker
+14.1points
- Latency+14.0
- Head freshness+0.0
- Availability+0.0
- Correctness−0.0
The parts add to +14.1, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+32.6points
- Latency+21.6
- Availability+9.7
- Correctness+0.7
- Head freshness+0.7
The parts add to +32.6, exactly — the score is a weighted sum, so it comes apart.