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
7d window · 3.2 days observed · generated 2026-08-28 02:04:05 UTC
| Metric | Tenderly | dRPC | Blast API | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 3 | 5 | 8 |
| Score | 97.6 | 91.8 | 84.5 | 61.8 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 99.97% | 99.94% | 99.98% | 83.57% |
| p50 latency | 19.7 ms | 33.8 ms | 105.1 ms | 265.3 ms |
| p95 latency | 45.5 ms | 71.1 ms | 122.6 ms | 4975.4 ms |
| p99 latency | 675.8 ms | 170.8 ms | 148.0 ms | 8455.9 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 97.38% |
| Head lag | 0.50 blocks | 0.36 blocks | 0.42 blocks | 0.91 blocks |
| Rate limited | 0 | 675 | 1,269 | 21,510 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 125,420 | 123,352 | 124,839 | 26,405 |
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
+5.8points
- Latency+5.9
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +5.8, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+13.1points
- Latency+13.2
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +13.1, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+35.7points
- Latency+28.2
- Availability+6.6
- Correctness+0.5
- Head freshness+0.5
The parts add to +35.7, exactly — the score is a weighted sum, so it comes apart.