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
6h window · 6.0 hours observed · generated 2026-08-27 20:23:02 UTC
| Metric | Tenderly | dRPC | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 1 | 3 | 5 | 6 |
| Score | 99.4 | 88.6 | 78.3 | 70.7 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.99% | 99.98% | 99.92% | 100.00% |
| p50 latency | 19.6 ms | 35.1 ms | 109.0 ms | 110.5 ms |
| p95 latency | 32.9 ms | 72.9 ms | 127.6 ms | 192.2 ms |
| p99 latency | 59.3 ms | 194.9 ms | 154.6 ms | 236.0 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.35 blocks | 0.41 blocks | 0.60 blocks |
| Rate limited | 0 | 24 | 67 | 1,404 |
| Unsupported | 0 | 0 | 0 | 18 |
| Samples | 8,721 | 8,582 | 8,709 | 2,071 |
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
+10.8points
- Latency+11.0
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +10.8, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+21.1points
- Latency+21.1
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +21.1, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+28.7points
- Latency+28.5
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +28.7, exactly — the score is a weighted sum, so it comes apart.