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-27 02:18:10 UTC
| Metric | Tenderly | dRPC | NodeReal | Blast API |
|---|---|---|---|---|
| Rank | 2 | 3 | 4 | 5 |
| Score | 99.1 | 91.2 | 86.6 | 84.1 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.98% | 99.92% | 100.00% | 99.98% |
| p50 latency | 19.8 ms | 34.1 ms | 87.2 ms | 104.5 ms |
| p95 latency | 36.8 ms | 69.2 ms | 100.0 ms | 121.1 ms |
| p99 latency | 212.1 ms | 171.8 ms | 124.9 ms | 140.7 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 99.99% |
| Head lag | 0.49 blocks | 0.38 blocks | 0.34 blocks | 0.42 blocks |
| Rate limited | 0 | 125 | 0 | 266 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 37,750 | 37,154 | 37,120 | 37,533 |
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
+12.5points
- Latency+12.7
- Head freshness−0.2
- Availability−0.0
- Correctness−0.0
The parts add to +12.5, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+15.0points
- Latency+15.1
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +15.0, exactly — the score is a weighted sum, so it comes apart.