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 01:53:32 UTC
| Metric | Tenderly | dRPC | NodeReal | Merkle |
|---|---|---|---|---|
| Rank | 1 | 3 | 4 | 6 |
| Score | 99.4 | 89.8 | 86.2 | 77.6 |
| Status | Excellent | Good | Good | Good |
| Availability | 99.99% | 99.86% | 99.99% | 100.00% |
| p50 latency | 19.0 ms | 34.1 ms | 87.0 ms | 105.9 ms |
| p95 latency | 32.2 ms | 73.2 ms | 99.3 ms | 193.5 ms |
| p99 latency | 71.8 ms | 179.0 ms | 122.1 ms | 220.4 ms |
| Correctness | 100.00% | 99.98% | 99.99% | 100.00% |
| Head lag | 0.50 blocks | 0.39 blocks | 0.33 blocks | 0.51 blocks |
| Rate limited | 0 | 33 | 0 | 1,481 |
| Unsupported | 0 | 0 | 0 | 18 |
| Samples | 9,516 | 9,383 | 9,380 | 2,128 |
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.6points
- Latency+9.6
- Head freshness−0.1
- Availability+0.1
- Correctness+0.0
The parts add to +9.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsNodeReal
+13.2points
- Latency+13.4
- Head freshness−0.2
- Correctness+0.0
- Availability+0.0
The parts add to +13.2, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+21.8points
- Latency+21.8
- Head freshness+0.0
- Availability−0.0
- Correctness+0.0
The parts add to +21.8, exactly — the score is a weighted sum, so it comes apart.