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 09:32:35 UTC
| Metric | Tenderly | dRPC | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 2 | 3 | 5 | 6 |
| Score | 99.1 | 88.0 | 78.1 | 70.0 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.98% | 99.93% | 99.99% | 100.00% |
| p50 latency | 18.6 ms | 31.6 ms | 105.0 ms | 105.4 ms |
| p95 latency | 33.0 ms | 65.8 ms | 120.5 ms | 194.3 ms |
| p99 latency | 113.7 ms | 160.0 ms | 147.4 ms | 228.8 ms |
| Correctness | 100.00% | 99.99% | 99.99% | 100.00% |
| Head lag | 0.48 blocks | 0.36 blocks | 0.42 blocks | 0.61 blocks |
| Rate limited | 0 | 40 | 127 | 1,424 |
| Unsupported | 0 | 0 | 0 | 15 |
| Samples | 8,966 | 8,827 | 8,961 | 2,048 |
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.1points
- Latency+11.3
- 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.
TenderlyvsBlast API
+21.1points
- Latency+21.2
- 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
+29.1points
- Latency+29.0
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +29.1, exactly — the score is a weighted sum, so it comes apart.