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 03:33:17 UTC
| Metric | Tenderly | dRPC | NodeReal | Blast API |
|---|---|---|---|---|
| Rank | 2 | 3 | 4 | 5 |
| Score | 99.1 | 91.2 | 85.6 | 83.6 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 100.00% | 99.98% | 99.61% | 99.99% |
| p50 latency | 18.4 ms | 32.4 ms | 87.6 ms | 103.8 ms |
| p95 latency | 31.6 ms | 62.4 ms | 99.2 ms | 119.1 ms |
| p99 latency | 54.4 ms | 162.8 ms | 116.4 ms | 147.1 ms |
| Correctness | 100.00% | 99.98% | 99.99% | 99.99% |
| Head lag | 0.47 blocks | 0.37 blocks | 0.34 blocks | 0.41 blocks |
| Rate limited | 0 | 7 | 0 | 32 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 9,012 | 8,855 | 8,828 | 9,007 |
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.5points
- Latency+13.5
- Availability+0.2
- Head freshness−0.2
- Correctness+0.0
The parts add to +13.5, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+15.6points
- Latency+15.6
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +15.6, exactly — the score is a weighted sum, so it comes apart.