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.9 days observed · generated 2026-08-27 18:59:19 UTC
| Metric | Tenderly | dRPC | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 2 | 3 | 5 | 6 |
| Score | 96.9 | 92.0 | 84.8 | 78.4 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.96% | 99.94% | 99.98% | 99.98% |
| p50 latency | 19.8 ms | 33.9 ms | 105.2 ms | 106.9 ms |
| p95 latency | 49.6 ms | 71.9 ms | 122.7 ms | 195.7 ms |
| p99 latency | 730.9 ms | 170.6 ms | 147.7 ms | 242.9 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 | 660 | 1,218 | 18,280 |
| Unsupported | 0 | 0 | 0 | 223 |
| Samples | 113,952 | 112,075 | 113,368 | 26,401 |
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
+4.9points
- Latency+5.0
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +4.9, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+12.1points
- Latency+12.2
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +12.1, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+18.5points
- Latency+18.5
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +18.5, exactly — the score is a weighted sum, so it comes apart.