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
24h window · 24 hours observed · generated 2026-08-28 17:31:59 UTC
| Metric | Tenderly | Blast API | Merkle |
|---|---|---|---|
| Rank | 1 | 5 | 6 |
| Score | 99.4 | 83.5 | 77.4 |
| Status | Excellent | Good | Good |
| Availability | 99.99% | 99.97% | 100.00% |
| p50 latency | 18.8 ms | 105.4 ms | 107.2 ms |
| p95 latency | 32.4 ms | 121.9 ms | 196.2 ms |
| p99 latency | 60.3 ms | 145.0 ms | 265.9 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.48 blocks | 0.41 blocks | 0.52 blocks |
| Rate limited | 0 | 353 | 6,147 |
| Unsupported | 0 | 0 | 72 |
| Samples | 38,160 | 38,145 | 8,908 |
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.
TenderlyvsBlast API
+15.9points
- Latency+16.0
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +15.9, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+22.0points
- Latency+21.9
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +22.0, exactly — the score is a weighted sum, so it comes apart.