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-27 05:17:58 UTC
| Metric | Tenderly | dRPC | Merkle |
|---|---|---|---|
| Rank | 2 | 3 | 6 |
| Score | 98.0 | 89.2 | 69.9 |
| Status | Excellent | Good | Degraded |
| Availability | 100.00% | 99.94% | 100.00% |
| p50 latency | 19.6 ms | 30.7 ms | 104.6 ms |
| p95 latency | 33.1 ms | 58.1 ms | 192.8 ms |
| p99 latency | 60.8 ms | 159.2 ms | 268.8 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.36 blocks | 0.72 blocks |
| Rate limited | 0 | 5 | 251 |
| Unsupported | 0 | 0 | 1 |
| Samples | 1,610 | 1,584 | 362 |
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
+8.8points
- Latency+8.9
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.8, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+28.1points
- Latency+27.9
- Head freshness+0.3
- Availability+0.0
- Correctness+0.0
The parts add to +28.1, exactly — the score is a weighted sum, so it comes apart.