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
24h window · 24 hours observed · generated 2026-08-28 21:12:30 UTC
| Metric | Tenderly | Merkle | 1RPC |
|---|---|---|---|
| Rank | 1 | 6 | 8 |
| Score | 99.4 | 77.4 | 59.4 |
| Status | Excellent | Good | Degraded |
| Availability | 99.99% | 100.00% | 77.78% |
| p50 latency | 18.8 ms | 107.3 ms | 1326.0 ms |
| p95 latency | 32.5 ms | 200.9 ms | 7406.7 ms |
| p99 latency | 61.0 ms | 263.5 ms | 9776.0 ms |
| Correctness | 99.99% | 100.00% | 96.96% |
| Head lag | 0.48 blocks | 0.50 blocks | 0.94 blocks |
| Rate limited | 0 | 6,053 | 6,446 |
| Unsupported | 0 | 73 | 0 |
| Samples | 37,644 | 8,735 | 7,736 |
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
+22.0points
- Latency+22.0
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +22.0, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+40.0points
- Latency+30.0
- Availability+8.9
- Correctness+0.6
- Head freshness+0.5
The parts add to +40.0, exactly — the score is a weighted sum, so it comes apart.