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.3 days observed · generated 2026-08-27 04:57:07 UTC
| Metric | Tenderly | Merkle | 1RPC |
|---|---|---|---|
| Rank | 2 | 6 | 8 |
| Score | 94.5 | 78.9 | 62.6 |
| Status | Excellent | Good | Degraded |
| Availability | 99.96% | 99.98% | 85.50% |
| p50 latency | 19.8 ms | 106.5 ms | 225.7 ms |
| p95 latency | 64.8 ms | 195.8 ms | 4391.3 ms |
| p99 latency | 851.1 ms | 244.4 ms | 7602.5 ms |
| Correctness | 99.99% | 100.00% | 97.48% |
| Head lag | 0.51 blocks | 0.47 blocks | 0.91 blocks |
| Rate limited | 0 | 14,690 | 15,651 |
| Unsupported | 0 | 180 | 0 |
| Samples | 91,204 | 21,109 | 19,333 |
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
+15.6points
- Latency+15.7
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +15.6, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+31.9points
- Latency+25.2
- Availability+5.8
- Correctness+0.5
- Head freshness+0.5
The parts add to +31.9, exactly — the score is a weighted sum, so it comes apart.