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.5 days observed · generated 2026-08-27 08:32:01 UTC
| Metric | Tenderly | dRPC | NodeReal |
|---|---|---|---|
| Rank | 2 | 3 | 4 |
| Score | 95.1 | 92.7 | 88.1 |
| Status | Excellent | Excellent | Good |
| Availability | 99.96% | 99.93% | 99.81% |
| p50 latency | 19.8 ms | 33.8 ms | 87.4 ms |
| p95 latency | 59.7 ms | 71.8 ms | 100.1 ms |
| p99 latency | 819.4 ms | 167.6 ms | 125.9 ms |
| Correctness | 99.99% | 99.99% | 99.99% |
| Head lag | 0.50 blocks | 0.36 blocks | 0.35 blocks |
| Rate limited | 0 | 601 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 96,993 | 95,404 | 95,370 |
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
+2.4points
- Latency+2.6
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +2.4, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsNodeReal
+7.1points
- Latency+7.2
- Head freshness−0.2
- Availability+0.1
- Correctness−0.0
The parts add to +7.1, exactly — the score is a weighted sum, so it comes apart.