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 06:20:20 UTC
| Metric | Tenderly | Merkle | MEV Blocker |
|---|---|---|---|
| Rank | 2 | 6 | 7 |
| Score | 98.9 | 70.1 | 69.5 |
| Status | Excellent | Degraded | Degraded |
| Availability | 100.00% | 100.00% | 99.92% |
| p50 latency | 18.7 ms | 104.8 ms | 118.6 ms |
| p95 latency | 32.4 ms | 193.2 ms | 207.0 ms |
| p99 latency | 64.9 ms | 283.4 ms | 225.0 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.47 blocks | 0.51 blocks | 0.40 blocks |
| Rate limited | 0 | 1,351 | 0 |
| Unsupported | 0 | 18 | 0 |
| Samples | 8,640 | 1,915 | 8,614 |
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
+28.7points
- Latency+28.7
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +28.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMEV Blocker
+29.4points
- Latency+29.4
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +29.4, exactly — the score is a weighted sum, so it comes apart.