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
1h window · 60 minutes observed · generated 2026-08-27 12:29:48 UTC
| Metric | Tenderly | dRPC | NodeReal | Merkle |
|---|---|---|---|---|
| Rank | 1 | 3 | 4 | 6 |
| Score | 99.4 | 84.6 | 83.1 | 70.5 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 100.00% | 99.94% | 100.00% | 100.00% |
| p50 latency | 21.0 ms | 33.9 ms | 87.4 ms | 112.0 ms |
| p95 latency | 34.2 ms | 90.2 ms | 98.8 ms | 204.6 ms |
| p99 latency | 66.8 ms | 193.6 ms | 120.9 ms | 217.6 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.50 blocks | 0.38 blocks | 0.32 blocks | 0.20 blocks |
| Rate limited | 0 | 9 | 0 | 253 |
| Unsupported | 0 | 0 | 0 | 2 |
| Samples | 1,622 | 1,587 | 1,584 | 368 |
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
+14.8points
- Latency+14.9
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +14.8, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsNodeReal
+16.3points
- Latency+16.5
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +16.3, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+28.9points
- Latency+29.3
- Head freshness−0.4
- Availability+0.0
- Correctness+0.0
The parts add to +28.9, exactly — the score is a weighted sum, so it comes apart.