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
1h window · 60 minutes observed · generated 2026-08-28 00:24:29 UTC
| Metric | Tenderly | dRPC | NodeReal | Blast API |
|---|---|---|---|---|
| Rank | 2 | 3 | 4 | 5 |
| Score | 99.2 | 91.3 | 85.9 | 83.7 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 100.00% | 100.00% | 100.00% | 100.00% |
| p50 latency | 17.1 ms | 31.5 ms | 87.4 ms | 103.4 ms |
| p95 latency | 30.9 ms | 61.8 ms | 98.8 ms | 119.8 ms |
| p99 latency | 56.7 ms | 150.1 ms | 110.8 ms | 146.6 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.46 blocks | 0.40 blocks | 0.38 blocks | 0.41 blocks |
| Rate limited | 0 | 1 | 0 | 0 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 1,614 | 1,564 | 1,568 | 1,605 |
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.9points
- Latency+8.0
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +7.9, 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.
TenderlyvsBlast API
+15.5points
- Latency+15.5
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +15.5, exactly — the score is a weighted sum, so it comes apart.