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.2 days observed · generated 2026-08-27 01:49:57 UTC
| Metric | Tenderly | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 3 | 6 | 7 |
| Score | 93.7 | 79.2 | 78.2 |
| Status | Excellent | Good | Good |
| Availability | 99.96% | 99.98% | 99.88% |
| p50 latency | 19.9 ms | 106.6 ms | 118.5 ms |
| p95 latency | 72.4 ms | 196.0 ms | 209.5 ms |
| p99 latency | 878.8 ms | 243.1 ms | 233.4 ms |
| Correctness | 99.99% | 100.00% | 99.99% |
| Head lag | 0.51 blocks | 0.47 blocks | 0.40 blocks |
| Rate limited | 0 | 13,878 | 2 |
| Unsupported | 0 | 169 | 0 |
| Samples | 86,155 | 19,971 | 85,995 |
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
+14.5points
- Latency+14.6
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +14.5, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMEV Blocker
+15.5points
- Latency+15.6
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +15.5, exactly — the score is a weighted sum, so it comes apart.