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-27 03:26:44 UTC
| Metric | Tenderly | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 2 | 6 | 7 |
| Score | 99.1 | 78.0 | 77.0 |
| Status | Excellent | Good | Good |
| Availability | 99.98% | 100.00% | 99.90% |
| p50 latency | 19.7 ms | 107.2 ms | 119.5 ms |
| p95 latency | 36.6 ms | 194.3 ms | 210.8 ms |
| p99 latency | 196.9 ms | 239.8 ms | 234.5 ms |
| Correctness | 99.99% | 100.00% | 99.99% |
| Head lag | 0.49 blocks | 0.46 blocks | 0.39 blocks |
| Rate limited | 0 | 6,111 | 2 |
| Unsupported | 0 | 81 | 0 |
| Samples | 37,976 | 8,741 | 37,932 |
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
+21.1points
- Latency+21.2
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +21.1, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMEV Blocker
+22.1points
- Latency+22.2
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +22.1, exactly — the score is a weighted sum, so it comes apart.