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-28 09:11:50 UTC
| Metric | Tenderly | dRPC | NodeReal | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 3 | 4 | 8 |
| Score | 99.4 | 91.3 | 86.5 | 58.8 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 99.99% | 99.97% | 99.90% | 76.33% |
| p50 latency | 19.0 ms | 33.1 ms | 87.4 ms | 1326.0 ms |
| p95 latency | 32.4 ms | 68.5 ms | 100.1 ms | 7406.7 ms |
| p99 latency | 57.2 ms | 189.7 ms | 136.5 ms | 9776.0 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 96.96% |
| Head lag | 0.47 blocks | 0.37 blocks | 0.34 blocks | 0.94 blocks |
| Rate limited | 0 | 77 | 0 | 6,441 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 37,609 | 36,987 | 36,936 | 7,736 |
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
+8.1points
- Latency+8.3
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.1, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsNodeReal
+12.9points
- Latency+13.1
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +12.9, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+40.6points
- Latency+30.0
- Availability+9.5
- Correctness+0.6
- Head freshness+0.5
The parts add to +40.6, exactly — the score is a weighted sum, so it comes apart.