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
6h window · 6.0 hours observed · generated 2026-08-27 17:33:37 UTC
| Metric | dRPC | MEV Blocker | 1RPC |
|---|---|---|---|
| Rank | 3 | 7 | 9 |
| Score | 89.6 | 69.5 | 0.0 |
| Status | Good | Degraded | Poor |
| Availability | 99.95% | 99.90% | 0.00% |
| p50 latency | 34.6 ms | 125.1 ms | 0.0 ms |
| p95 latency | 68.4 ms | 217.4 ms | 0.0 ms |
| p99 latency | 177.3 ms | 242.9 ms | 0.0 ms |
| Correctness | 99.99% | 100.00% | not measured |
| Head lag | 0.36 blocks | 0.40 blocks | no cohort |
| Rate limited | 23 | 0 | 1,560 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,856 | 8,984 | 1,789 |
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
+20.1points
- Latency+20.1
- Head freshness+0.0
- Availability+0.0
- Correctness−0.0
The parts add to +20.1, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+89.6points
- Availability+40.0
- Latency*+20.1
- Correctness*+20.0
- Head freshness*+9.6
The parts add to +89.6, exactly — the score is a weighted sum, so it comes apart. Components marked * were measured for only one of the two; the other’s weight is spread across what it does have, which is why the two sides can carry different weights for the same row.