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
24h window · 24 hours observed · generated 2026-08-26 22:34:24 UTC
| Metric | Tenderly | dRPC | NodeReal |
|---|---|---|---|
| Rank | 2 | 3 | 4 |
| Score | 98.8 | 91.4 | 86.6 |
| Status | Excellent | Excellent | Good |
| Availability | 99.97% | 99.92% | 100.00% |
| p50 latency | 19.8 ms | 34.1 ms | 87.4 ms |
| p95 latency | 37.4 ms | 68.4 ms | 100.2 ms |
| p99 latency | 261.0 ms | 167.7 ms | 124.7 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.37 blocks | 0.35 blocks |
| Rate limited | 0 | 122 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 38,220 | 37,583 | 37,543 |
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
+7.5points
- Latency+7.6
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +7.5, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsNodeReal
+12.2points
- Latency+12.4
- Head freshness−0.2
- Availability−0.0
- Correctness−0.0
The parts add to +12.2, exactly — the score is a weighted sum, so it comes apart.