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
6h window · 6.0 hours observed · generated 2026-08-28 01:31:25 UTC
| Metric | Tenderly | dRPC | NodeReal | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 3 | 4 | 8 |
| Score | 99.4 | 91.6 | 86.3 | 60.3 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 100.00% | 99.97% | 99.97% | 79.94% |
| p50 latency | 18.6 ms | 32.5 ms | 87.2 ms | 1326.0 ms |
| p95 latency | 31.9 ms | 63.5 ms | 98.8 ms | 7406.7 ms |
| p99 latency | 54.3 ms | 173.7 ms | 116.1 ms | 9776.0 ms |
| Correctness | 100.00% | 99.98% | 99.97% | 96.96% |
| Head lag | 0.46 blocks | 0.37 blocks | 0.34 blocks | 0.94 blocks |
| Rate limited | 0 | 13 | 0 | 1,511 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,960 | 8,794 | 8,784 | 2,080 |
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.8points
- Latency+7.9
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +7.8, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsNodeReal
+13.2points
- Latency+13.3
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +13.2, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+39.2points
- Latency+30.0
- Availability+8.0
- Correctness+0.6
- Head freshness+0.6
The parts add to +39.2, exactly — the score is a weighted sum, so it comes apart.