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:38:17 UTC
| Metric | dRPC | NodeReal | MEV Blocker | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 4 | 7 | 8 |
| Score | 93.7 | 88.9 | 77.9 | 63.8 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.93% | 99.78% | 99.88% | 88.36% |
| p50 latency | 34.1 ms | 87.4 ms | 118.5 ms | 189.3 ms |
| p95 latency | 72.7 ms | 99.9 ms | 209.4 ms | 2922.0 ms |
| p99 latency | 169.3 ms | 123.8 ms | 233.5 ms | 6561.8 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 97.72% |
| Head lag | 0.36 blocks | 0.35 blocks | 0.40 blocks | 0.90 blocks |
| Rate limited | 548 | 0 | 1 | 14,187 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 81,218 | 81,161 | 82,454 | 17,301 |
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.
dRPCvsNodeReal
+4.8points
- Latency+4.7
- Availability+0.1
- Head freshness−0.0
- Correctness−0.0
The parts add to +4.8, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMEV Blocker
+15.8points
- Latency+15.8
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +15.8, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+29.9points
- Latency+24.2
- Availability+4.6
- Head freshness+0.6
- Correctness+0.5
The parts add to +29.9, exactly — the score is a weighted sum, so it comes apart.