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
30d window · 3.5 days observed · generated 2026-08-28 09:07:51 UTC
| Metric | Tenderly | dRPC | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 2 | 3 | 5 | 6 |
| Score | 98.0 | 91.5 | 84.3 | 78.1 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.97% | 99.94% | 99.98% | 99.99% |
| p50 latency | 19.6 ms | 33.6 ms | 105.1 ms | 106.8 ms |
| p95 latency | 42.4 ms | 70.9 ms | 122.2 ms | 195.4 ms |
| p99 latency | 624.9 ms | 172.6 ms | 147.3 ms | 245.2 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.36 blocks | 0.42 blocks | 0.49 blocks |
| Rate limited | 0 | 692 | 1,443 | 22,020 |
| Unsupported | 0 | 0 | 0 | 271 |
| Samples | 136,871 | 134,618 | 136,297 | 31,836 |
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
+6.5points
- Latency+6.7
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +6.5, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+13.7points
- Latency+13.8
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +13.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+19.9points
- Latency+19.9
- Availability−0.0
- Head freshness−0.0
- Correctness−0.0
The parts add to +19.9, exactly — the score is a weighted sum, so it comes apart.