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
7d window · 2.3 days observed · generated 2026-08-27 02:57:28 UTC
| Metric | Tenderly | dRPC | NodeReal | Merkle |
|---|---|---|---|---|
| Rank | 2 | 3 | 4 | 6 |
| Score | 94.0 | 93.5 | 88.9 | 79.1 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.96% | 99.93% | 99.79% | 99.98% |
| p50 latency | 19.9 ms | 34.0 ms | 87.3 ms | 106.6 ms |
| p95 latency | 69.4 ms | 72.6 ms | 99.9 ms | 196.0 ms |
| p99 latency | 868.9 ms | 169.1 ms | 123.5 ms | 243.1 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 100.00% |
| Head lag | 0.51 blocks | 0.36 blocks | 0.35 blocks | 0.46 blocks |
| Rate limited | 0 | 569 | 0 | 14,187 |
| Unsupported | 0 | 0 | 0 | 174 |
| Samples | 87,977 | 86,521 | 86,468 | 20,399 |
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
+0.5points
- Latency+0.6
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +0.5, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsNodeReal
+5.1points
- Latency+5.3
- Head freshness−0.2
- Availability+0.1
- Correctness−0.0
The parts add to +5.1, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+15.0points
- Latency+15.0
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +15.0, exactly — the score is a weighted sum, so it comes apart.