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
30d window · 3.9 days observed · generated 2026-08-28 19:24:13 UTC
| Metric | Tenderly | Merkle | 1RPC |
|---|---|---|---|
| Rank | 2 | 6 | 8 |
| Score | 98.5 | 78.0 | 61.7 |
| Status | Excellent | Good | Degraded |
| Availability | 99.97% | 99.99% | 83.16% |
| p50 latency | 19.6 ms | 107.0 ms | 265.3 ms |
| p95 latency | 40.3 ms | 195.8 ms | 4975.4 ms |
| p99 latency | 560.6 ms | 245.1 ms | 8455.9 ms |
| Correctness | 99.99% | 100.00% | 97.38% |
| Head lag | 0.49 blocks | 0.49 blocks | 0.91 blocks |
| Rate limited | 0 | 24,667 | 26,353 |
| Unsupported | 0 | 297 | 0 |
| Samples | 153,533 | 35,634 | 31,957 |
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
+20.5points
- Latency+20.5
- Availability−0.0
- Head freshness−0.0
- Correctness−0.0
The parts add to +20.5, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+36.8points
- Latency+29.1
- Availability+6.7
- Correctness+0.5
- Head freshness+0.5
The parts add to +36.8, exactly — the score is a weighted sum, so it comes apart.