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 13:06:31 UTC
| Metric | Tenderly | Blast API | Merkle |
|---|---|---|---|
| Rank | 1 | 5 | 6 |
| Score | 99.4 | 78.7 | 70.1 |
| Status | Excellent | Good | Degraded |
| Availability | 99.94% | 100.00% | 100.00% |
| p50 latency | 20.0 ms | 107.6 ms | 108.0 ms |
| p95 latency | 35.0 ms | 124.7 ms | 200.3 ms |
| p99 latency | 103.2 ms | 153.6 ms | 231.3 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.40 blocks | 0.49 blocks |
| Rate limited | 0 | 78 | 1,324 |
| Unsupported | 0 | 0 | 16 |
| Samples | 8,284 | 8,279 | 1,965 |
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
+20.7points
- Latency+20.9
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +20.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+29.3points
- Latency+29.3
- Availability−0.0
- Head freshness+0.0
- Correctness+0.0
The parts add to +29.3, exactly — the score is a weighted sum, so it comes apart.