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.1 days observed · generated 2026-08-26 23:46:10 UTC
| Metric | Tenderly | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 3 | 6 | 7 |
| Score | 92.1 | 78.9 | 77.9 |
| Status | Excellent | Good | Good |
| Availability | 99.96% | 99.98% | 99.88% |
| p50 latency | 20.0 ms | 106.7 ms | 118.5 ms |
| p95 latency | 80.5 ms | 196.1 ms | 209.4 ms |
| p99 latency | 900.3 ms | 243.2 ms | 233.5 ms |
| Correctness | 99.99% | 100.00% | 99.99% |
| Head lag | 0.51 blocks | 0.47 blocks | 0.40 blocks |
| Rate limited | 0 | 13,345 | 1 |
| Unsupported | 0 | 161 | 0 |
| Samples | 82,818 | 19,218 | 82,664 |
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
+13.2points
- Latency+13.3
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +13.2, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMEV Blocker
+14.1points
- Latency+14.2
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +14.1, exactly — the score is a weighted sum, so it comes apart.