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
Side by side
30d window · 2.2 days observed · generated 2026-08-27 01:32:02 UTC
| Metric | dRPC | MEV Blocker | 1RPC |
|---|---|---|---|
| Rank | 2 | 7 | 8 |
| Score | 93.8 | 78.2 | 62.6 |
| Status | Excellent | Good | Degraded |
| Availability | 99.93% | 99.88% | 85.50% |
| p50 latency | 34.1 ms | 118.5 ms | 225.7 ms |
| p95 latency | 72.5 ms | 209.4 ms | 4391.3 ms |
| p99 latency | 169.1 ms | 233.4 ms | 7602.5 ms |
| Correctness | 99.99% | 99.99% | 97.48% |
| Head lag | 0.36 blocks | 0.40 blocks | 0.91 blocks |
| Rate limited | 558 | 2 | 14,690 |
| Unsupported | 0 | 0 | 0 |
| Samples | 84,244 | 85,514 | 18,236 |
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.
dRPCvsMEV Blocker
+15.6points
- Latency+15.6
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +15.6, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+31.2points
- Latency+24.3
- Availability+5.8
- Head freshness+0.6
- Correctness+0.5
The parts add to +31.2, exactly — the score is a weighted sum, so it comes apart.