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 12:27:09 UTC
| Metric | Tenderly | dRPC | NodeReal | Merkle |
|---|---|---|---|---|
| Rank | 1 | 3 | 4 | 6 |
| Score | 99.4 | 86.9 | 82.5 | 70.0 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.93% | 99.95% | 100.00% | 100.00% |
| p50 latency | 19.6 ms | 33.1 ms | 87.8 ms | 106.8 ms |
| p95 latency | 35.1 ms | 77.7 ms | 99.8 ms | 202.1 ms |
| p99 latency | 126.9 ms | 176.0 ms | 123.1 ms | 231.3 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.47 blocks | 0.36 blocks | 0.34 blocks | 0.50 blocks |
| Rate limited | 0 | 45 | 0 | 1,428 |
| Unsupported | 0 | 0 | 0 | 17 |
| Samples | 8,835 | 8,696 | 8,678 | 2,092 |
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
+12.5points
- Latency+12.7
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +12.5, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsNodeReal
+16.9points
- Latency+17.1
- Head freshness−0.2
- Availability−0.0
- Correctness+0.0
The parts add to +16.9, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+29.4points
- Latency+29.4
- Head freshness+0.0
- Availability−0.0
- Correctness+0.0
The parts add to +29.4, exactly — the score is a weighted sum, so it comes apart.