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
1h window · 60 minutes observed · generated 2026-08-28 00:23:57 UTC
| Metric | Tenderly | Merkle | 1RPC |
|---|---|---|---|
| Rank | 2 | 6 | 8 |
| Score | 99.2 | 77.7 | 60.1 |
| Status | Excellent | Good | Degraded |
| Availability | 100.00% | 100.00% | 79.11% |
| p50 latency | 17.1 ms | 107.0 ms | 1367.5 ms |
| p95 latency | 30.9 ms | 202.2 ms | 7705.9 ms |
| p99 latency | 56.7 ms | 316.7 ms | 9776.0 ms |
| Correctness | 100.00% | 100.00% | 97.66% |
| Head lag | 0.46 blocks | 0.43 blocks | 0.93 blocks |
| Rate limited | 0 | 256 | 182 |
| Unsupported | 0 | 2 | 0 |
| Samples | 1,628 | 379 | 527 |
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.5
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +21.5, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+39.1points
- Latency+29.7
- Availability+8.4
- Head freshness+0.5
- Correctness+0.5
The parts add to +39.1, exactly — the score is a weighted sum, so it comes apart.