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
- NodeReal
- Blast API
- Tenderly
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
7d window · 44 hours observed · generated 2026-08-26 16:25:08 UTC
| Metric | dRPC | Merkle | MEV Blocker | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 6 | 7 | 8 |
| Score | 93.5 | 78.4 | 77.5 | 64.0 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.94% | 99.97% | 99.87% | 88.84% |
| p50 latency | 33.8 ms | 106.5 ms | 118.1 ms | 189.3 ms |
| p95 latency | 72.0 ms | 196.8 ms | 208.7 ms | 2922.0 ms |
| p99 latency | 166.5 ms | 245.4 ms | 232.9 ms | 6561.8 ms |
| Correctness | 99.99% | 100.00% | 99.98% | 97.72% |
| Head lag | 0.35 blocks | 0.47 blocks | 0.39 blocks | 0.90 blocks |
| Rate limited | 503 | 11,499 | 0 | 12,179 |
| Unsupported | 0 | 140 | 0 | 0 |
| Samples | 69,727 | 16,558 | 70,765 | 14,999 |
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
+15.1points
- Latency+15.0
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +15.1, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMEV Blocker
+16.0points
- Latency+15.9
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +16.0, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+29.5points
- Latency+24.0
- Availability+4.4
- Head freshness+0.6
- Correctness+0.5
The parts add to +29.5, exactly — the score is a weighted sum, so it comes apart.