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
30d window · 2.7 days observed · generated 2026-08-27 12:27:43 UTC
| Metric | Tenderly | dRPC | NodeReal | Merkle |
|---|---|---|---|---|
| Rank | 2 | 3 | 4 | 6 |
| Score | 95.7 | 92.4 | 87.9 | 78.5 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.96% | 99.93% | 99.82% | 99.98% |
| p50 latency | 19.8 ms | 33.8 ms | 87.4 ms | 106.5 ms |
| p95 latency | 55.7 ms | 72.1 ms | 100.0 ms | 196.3 ms |
| p99 latency | 792.1 ms | 168.5 ms | 125.7 ms | 243.4 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 100.00% |
| Head lag | 0.50 blocks | 0.36 blocks | 0.35 blocks | 0.48 blocks |
| Rate limited | 0 | 637 | 0 | 16,619 |
| Unsupported | 0 | 0 | 0 | 201 |
| Samples | 103,369 | 101,670 | 101,624 | 23,933 |
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
+3.4points
- Latency+3.5
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +3.4, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsNodeReal
+7.9points
- Latency+8.0
- Head freshness−0.2
- Availability+0.1
- Correctness−0.0
The parts add to +7.9, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+17.2points
- Latency+17.2
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +17.2, exactly — the score is a weighted sum, so it comes apart.