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
24h window · 24 hours observed · generated 2026-08-27 12:30:02 UTC
| Metric | Tenderly | dRPC | NodeReal | Merkle |
|---|---|---|---|---|
| Rank | 1 | 3 | 4 | 6 |
| Score | 99.4 | 90.3 | 86.4 | 77.8 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.97% | 99.91% | 100.00% | 100.00% |
| p50 latency | 19.4 ms | 34.2 ms | 87.3 ms | 107.0 ms |
| p95 latency | 34.8 ms | 73.1 ms | 100.1 ms | 194.6 ms |
| p99 latency | 94.8 ms | 173.0 ms | 128.3 ms | 235.0 ms |
| Correctness | 100.00% | 99.99% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.38 blocks | 0.34 blocks | 0.50 blocks |
| Rate limited | 0 | 163 | 0 | 6,065 |
| Unsupported | 0 | 0 | 0 | 71 |
| Samples | 38,040 | 37,448 | 37,434 | 8,707 |
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.0points
- Latency+9.2
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +9.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsNodeReal
+13.0points
- Latency+13.2
- Head freshness−0.2
- Availability−0.0
- Correctness+0.0
The parts add to +13.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+21.6points
- Latency+21.6
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +21.6, exactly — the score is a weighted sum, so it comes apart.