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-27 18:37:27 UTC
| Metric | Tenderly | Merkle | 1RPC |
|---|---|---|---|
| Rank | 1 | 6 | 8 |
| Score | 99.4 | 78.0 | 57.8 |
| Status | Excellent | Good | Degraded |
| Availability | 99.98% | 100.00% | 73.97% |
| p50 latency | 19.3 ms | 107.4 ms | 2024.4 ms |
| p95 latency | 33.9 ms | 193.7 ms | 6590.4 ms |
| p99 latency | 75.5 ms | 235.0 ms | 9196.2 ms |
| Correctness | 100.00% | 100.00% | 96.63% |
| Head lag | 0.48 blocks | 0.53 blocks | 0.95 blocks |
| Rate limited | 0 | 6,036 | 6,571 |
| Unsupported | 0 | 75 | 0 |
| Samples | 38,245 | 8,757 | 7,888 |
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
+21.5points
- Latency+21.4
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +21.5, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+41.6points
- Latency+30.0
- Availability+10.4
- Correctness+0.7
- Head freshness+0.5
The parts add to +41.6, exactly — the score is a weighted sum, so it comes apart.