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
7d window · 2.7 days observed · generated 2026-08-27 14:18:05 UTC
| Metric | Merkle | MEV Blocker | 1RPC |
|---|---|---|---|
| Rank | 6 | 7 | 8 |
| Score | 78.5 | 77.6 | 62.4 |
| Status | Good | Good | Degraded |
| Availability | 99.98% | 99.89% | 84.99% |
| p50 latency | 106.6 ms | 118.9 ms | 225.7 ms |
| p95 latency | 196.1 ms | 209.7 ms | 4391.3 ms |
| p99 latency | 243.1 ms | 233.3 ms | 7602.5 ms |
| Correctness | 100.00% | 99.99% | 97.48% |
| Head lag | 0.48 blocks | 0.40 blocks | 0.91 blocks |
| Rate limited | 17,094 | 3 | 18,259 |
| Unsupported | 207 | 0 | 0 |
| Samples | 24,634 | 106,156 | 22,326 |
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 Merkle, the highest scorer of those selected.
MerklevsMEV Blocker
+0.9points
- Latency+0.9
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +0.9, exactly — the score is a weighted sum, so it comes apart.
Merklevs1RPC
+16.1points
- Latency+9.1
- Availability+6.0
- Correctness+0.5
- Head freshness+0.5
The parts add to +16.1, exactly — the score is a weighted sum, so it comes apart.