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:36:14 UTC
| Metric | Tenderly | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 2 | 6 | 7 |
| Score | 94.4 | 78.9 | 78.0 |
| Status | Excellent | Good | Good |
| Availability | 99.96% | 99.98% | 99.89% |
| p50 latency | 19.8 ms | 106.5 ms | 118.5 ms |
| p95 latency | 65.7 ms | 195.9 ms | 209.3 ms |
| p99 latency | 854.4 ms | 243.2 ms | 233.0 ms |
| Correctness | 99.99% | 100.00% | 99.99% |
| Head lag | 0.51 blocks | 0.46 blocks | 0.40 blocks |
| Rate limited | 0 | 14,583 | 2 |
| Unsupported | 0 | 180 | 0 |
| Samples | 90,634 | 20,962 | 90,469 |
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
+15.5points
- Latency+15.6
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +15.5, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMEV Blocker
+16.4points
- Latency+16.5
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +16.4, exactly — the score is a weighted sum, so it comes apart.