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.3 days observed · generated 2026-08-27 04:01:20 UTC
| Metric | dRPC | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 3 | 6 | 7 |
| Score | 93.4 | 79.0 | 78.1 |
| Status | Excellent | Good | Good |
| Availability | 99.93% | 99.98% | 99.89% |
| p50 latency | 34.0 ms | 106.5 ms | 118.5 ms |
| p95 latency | 72.4 ms | 196.2 ms | 209.4 ms |
| p99 latency | 169.0 ms | 244.4 ms | 233.0 ms |
| Correctness | 99.99% | 100.00% | 99.99% |
| Head lag | 0.36 blocks | 0.47 blocks | 0.40 blocks |
| Rate limited | 575 | 14,452 | 2 |
| Unsupported | 0 | 179 | 0 |
| Samples | 88,216 | 20,771 | 89,532 |
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
+14.4points
- Latency+14.3
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +14.4, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMEV Blocker
+15.3points
- Latency+15.2
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +15.3, exactly — the score is a weighted sum, so it comes apart.