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:45:22 UTC
| Metric | Tenderly | dRPC | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 3 | 6 | 8 |
| Score | 99.1 | 91.5 | 77.7 | 60.3 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 100.00% | 100.00% | 100.00% | 79.94% |
| p50 latency | 17.1 ms | 31.8 ms | 102.9 ms | 1326.0 ms |
| p95 latency | 30.6 ms | 60.1 ms | 202.2 ms | 7406.7 ms |
| p99 latency | 48.9 ms | 143.0 ms | 316.7 ms | 9776.0 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 96.96% |
| Head lag | 0.47 blocks | 0.36 blocks | 0.40 blocks | 0.94 blocks |
| Rate limited | 0 | 1 | 254 | 231 |
| Unsupported | 0 | 0 | 2 | 0 |
| Samples | 1,603 | 1,576 | 361 | 617 |
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.
TenderlyvsdRPC
+7.6points
- Latency+7.7
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +7.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+21.4points
- Latency+21.5
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.4, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+38.8points
- Latency+29.7
- Availability+8.0
- Correctness+0.6
- Head freshness+0.5
The parts add to +38.8, exactly — the score is a weighted sum, so it comes apart.