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.2 days observed · generated 2026-08-27 01:54:16 UTC
| Metric | dRPC | Tenderly | NodeReal | Merkle |
|---|---|---|---|---|
| Rank | 2 | 3 | 4 | 6 |
| Score | 93.8 | 93.7 | 89.1 | 79.2 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.93% | 99.96% | 99.78% | 99.98% |
| p50 latency | 34.0 ms | 19.9 ms | 87.4 ms | 106.6 ms |
| p95 latency | 72.6 ms | 72.0 ms | 99.9 ms | 195.9 ms |
| p99 latency | 169.0 ms | 878.1 ms | 123.6 ms | 243.1 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 100.00% |
| Head lag | 0.36 blocks | 0.51 blocks | 0.35 blocks | 0.46 blocks |
| Rate limited | 561 | 0 | 0 | 13,893 |
| Unsupported | 0 | 0 | 0 | 170 |
| Samples | 84,841 | 86,273 | 84,790 | 20,006 |
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 dRPC, the highest scorer of those selected.
dRPCvsTenderly
+0.0points
- Head freshness+0.2
- Latency−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +0.0, exactly — the score is a weighted sum, so it comes apart.
dRPCvsNodeReal
+4.7points
- Latency+4.7
- Availability+0.1
- Head freshness−0.0
- Correctness+0.0
The parts add to +4.7, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+14.6points
- Latency+14.5
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +14.6, exactly — the score is a weighted sum, so it comes apart.