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
6h window · 6.0 hours observed · generated 2026-08-27 13:43:31 UTC
| Metric | Tenderly | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 1 | 6 | 7 |
| Score | 99.4 | 70.2 | 69.5 |
| Status | Excellent | Degraded | Degraded |
| Availability | 99.95% | 100.00% | 99.89% |
| p50 latency | 20.1 ms | 108.8 ms | 123.3 ms |
| p95 latency | 34.9 ms | 200.3 ms | 213.7 ms |
| p99 latency | 96.9 ms | 230.9 ms | 235.7 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.49 blocks | 0.39 blocks |
| Rate limited | 0 | 1,456 | 1 |
| Unsupported | 0 | 18 | 0 |
| Samples | 9,279 | 2,179 | 9,250 |
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
+29.2points
- Latency+29.2
- Availability−0.0
- Head freshness+0.0
- Correctness+0.0
The parts add to +29.2, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMEV Blocker
+29.9points
- Latency+30.0
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +29.9, exactly — the score is a weighted sum, so it comes apart.