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 18:37:27 UTC
| Metric | Tenderly | dRPC | NodeReal | Merkle |
|---|---|---|---|---|
| Rank | 1 | 3 | 4 | 6 |
| Score | 99.4 | 91.1 | 86.7 | 78.0 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.98% | 99.94% | 100.00% | 100.00% |
| p50 latency | 19.3 ms | 33.8 ms | 87.4 ms | 107.4 ms |
| p95 latency | 33.9 ms | 70.6 ms | 100.0 ms | 193.7 ms |
| p99 latency | 75.5 ms | 173.8 ms | 129.8 ms | 235.0 ms |
| Correctness | 100.00% | 99.99% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.37 blocks | 0.34 blocks | 0.53 blocks |
| Rate limited | 0 | 137 | 0 | 6,036 |
| Unsupported | 0 | 0 | 0 | 75 |
| Samples | 38,245 | 37,649 | 37,650 | 8,757 |
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.3points
- Latency+8.5
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.3, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsNodeReal
+12.7points
- Latency+12.9
- Head freshness−0.2
- Availability−0.0
- Correctness+0.0
The parts add to +12.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+21.5points
- Latency+21.4
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +21.5, exactly — the score is a weighted sum, so it comes apart.