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 · 2.3 days observed · generated 2026-08-27 04:01:20 UTC
| Metric | Tenderly | dRPC | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 2 | 3 | 5 | 6 |
| Score | 94.3 | 93.4 | 85.8 | 79.0 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.96% | 99.93% | 99.98% | 99.98% |
| p50 latency | 19.8 ms | 34.0 ms | 104.5 ms | 106.5 ms |
| p95 latency | 67.2 ms | 72.4 ms | 122.1 ms | 196.2 ms |
| p99 latency | 860.0 ms | 169.0 ms | 144.2 ms | 244.4 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 100.00% |
| Head lag | 0.51 blocks | 0.36 blocks | 0.42 blocks | 0.47 blocks |
| Rate limited | 0 | 575 | 987 | 14,452 |
| Unsupported | 0 | 0 | 0 | 179 |
| Samples | 89,695 | 88,216 | 89,145 | 20,771 |
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
+0.9points
- Latency+1.1
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +0.9, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+8.4points
- Latency+8.5
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +8.4, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+15.3points
- Latency+15.3
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +15.3, exactly — the score is a weighted sum, so it comes apart.