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
24h window · 24 hours observed · generated 2026-08-26 11:52:41 UTC
| Metric | Tenderly | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 4 | 6 | 7 |
| Score | 86.2 | 78.3 | 77.4 |
| Status | Good | Good | Good |
| Availability | 99.95% | 99.95% | 99.85% |
| p50 latency | 20.5 ms | 106.5 ms | 118.7 ms |
| p95 latency | 114.7 ms | 196.9 ms | 209.9 ms |
| p99 latency | 972.2 ms | 243.0 ms | 235.4 ms |
| Correctness | 99.98% | 100.00% | 99.98% |
| Head lag | 0.51 blocks | 0.47 blocks | 0.39 blocks |
| Rate limited | 0 | 6,239 | 0 |
| Unsupported | 0 | 79 | 0 |
| Samples | 38,727 | 9,063 | 38,616 |
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 Tenderly, the highest scorer of those selected.
TenderlyvsMerkle
+8.0points
- Latency+8.0
- Head freshness−0.0
- Correctness−0.0
- Availability−0.0
The parts add to +8.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMEV Blocker
+8.9points
- Latency+9.0
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +8.9, exactly — the score is a weighted sum, so it comes apart.