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 22:00:33 UTC
| Metric | Tenderly | dRPC | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 1 | 3 | 5 | 6 |
| Score | 99.4 | 88.4 | 78.4 | 70.7 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 100.00% | 99.99% | 99.91% | 100.00% |
| p50 latency | 19.0 ms | 34.7 ms | 108.1 ms | 109.6 ms |
| p95 latency | 32.6 ms | 71.9 ms | 125.8 ms | 191.8 ms |
| p99 latency | 56.1 ms | 196.2 ms | 152.9 ms | 231.9 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.47 blocks | 0.35 blocks | 0.41 blocks | 0.57 blocks |
| Rate limited | 0 | 19 | 44 | 1,297 |
| Unsupported | 0 | 0 | 0 | 12 |
| Samples | 8,112 | 7,987 | 8,105 | 1,933 |
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
+11.0points
- Latency+11.2
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +11.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+21.0points
- Latency+21.1
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+28.7points
- Latency+28.6
- 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.