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
6h window · 6.0 hours observed · generated 2026-08-27 17:57:45 UTC
| Metric | Tenderly | dRPC | NodeReal | Merkle |
|---|---|---|---|---|
| Rank | 1 | 3 | 4 | 6 |
| Score | 99.4 | 89.5 | 82.9 | 70.8 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.98% | 99.96% | 100.00% | 100.00% |
| p50 latency | 20.3 ms | 34.6 ms | 87.5 ms | 110.7 ms |
| p95 latency | 33.4 ms | 68.7 ms | 99.5 ms | 191.8 ms |
| p99 latency | 65.2 ms | 182.6 ms | 127.5 ms | 235.0 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.36 blocks | 0.33 blocks | 0.56 blocks |
| Rate limited | 0 | 26 | 0 | 1,527 |
| Unsupported | 0 | 0 | 0 | 20 |
| Samples | 9,668 | 9,504 | 9,500 | 2,250 |
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
+9.9points
- Latency+10.0
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +9.9, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsNodeReal
+16.5points
- Latency+16.7
- Head freshness−0.2
- Availability−0.0
- Correctness−0.0
The parts add to +16.5, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+28.6points
- Latency+28.5
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +28.6, exactly — the score is a weighted sum, so it comes apart.