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 · 2.7 days observed · generated 2026-08-27 14:19:05 UTC
| Metric | Tenderly | dRPC | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 2 | 3 | 5 | 6 |
| Score | 96.1 | 92.3 | 85.0 | 78.5 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.96% | 99.93% | 99.98% | 99.98% |
| p50 latency | 19.8 ms | 33.8 ms | 104.9 ms | 106.6 ms |
| p95 latency | 53.7 ms | 71.9 ms | 122.3 ms | 196.1 ms |
| p99 latency | 774.8 ms | 168.3 ms | 146.3 ms | 243.1 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 100.00% |
| Head lag | 0.50 blocks | 0.36 blocks | 0.42 blocks | 0.48 blocks |
| Rate limited | 0 | 641 | 1,154 | 17,095 |
| Unsupported | 0 | 0 | 0 | 207 |
| Samples | 106,383 | 104,624 | 105,809 | 24,635 |
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
+3.8points
- Latency+4.0
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +3.8, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+11.1points
- Latency+11.2
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +11.1, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+17.6points
- Latency+17.6
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +17.6, exactly — the score is a weighted sum, so it comes apart.