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-27 19:59:05 UTC
| Metric | Tenderly | dRPC | NodeReal | Blast API |
|---|---|---|---|---|
| Rank | 1 | 3 | 4 | 5 |
| Score | 99.4 | 88.7 | 83.0 | 78.3 |
| Status | Excellent | Good | Good | Good |
| Availability | 99.99% | 99.98% | 100.00% | 99.92% |
| p50 latency | 19.7 ms | 35.2 ms | 87.3 ms | 109.1 ms |
| p95 latency | 33.2 ms | 72.5 ms | 99.2 ms | 128.0 ms |
| p99 latency | 60.2 ms | 200.7 ms | 124.1 ms | 155.0 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.36 blocks | 0.34 blocks | 0.41 blocks |
| Rate limited | 0 | 20 | 0 | 72 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 9,692 | 9,543 | 9,537 | 9,683 |
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
+10.7points
- Latency+10.9
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +10.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsNodeReal
+16.4points
- Latency+16.5
- Head freshness−0.2
- Availability−0.0
- Correctness−0.0
The parts add to +16.4, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+21.1points
- Latency+21.2
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +21.1, exactly — the score is a weighted sum, so it comes apart.