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 · 3.2 days observed · generated 2026-08-28 01:28:51 UTC
| Metric | Tenderly | dRPC | NodeReal | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 3 | 4 | 8 |
| Score | 97.5 | 91.8 | 87.3 | 61.8 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 99.97% | 99.94% | 99.85% | 83.57% |
| p50 latency | 19.7 ms | 33.8 ms | 87.4 ms | 265.3 ms |
| p95 latency | 45.7 ms | 71.2 ms | 99.9 ms | 4975.4 ms |
| p99 latency | 679.2 ms | 170.9 ms | 125.0 ms | 8455.9 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 97.38% |
| Head lag | 0.50 blocks | 0.36 blocks | 0.34 blocks | 0.91 blocks |
| Rate limited | 0 | 674 | 0 | 21,344 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 124,472 | 122,414 | 122,359 | 26,216 |
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
+5.7points
- Latency+5.9
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +5.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsNodeReal
+10.2points
- Latency+10.4
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +10.2, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+35.7points
- Latency+28.1
- Availability+6.6
- Correctness+0.5
- Head freshness+0.5
The parts add to +35.7, exactly — the score is a weighted sum, so it comes apart.