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-28 02:09:27 UTC
| Metric | Tenderly | Blast API | Merkle |
|---|---|---|---|
| Rank | 2 | 5 | 6 |
| Score | 99.3 | 83.5 | 77.8 |
| Status | Excellent | Good | Good |
| Availability | 100.00% | 99.99% | 100.00% |
| p50 latency | 18.5 ms | 104.1 ms | 106.4 ms |
| p95 latency | 31.9 ms | 119.8 ms | 192.9 ms |
| p99 latency | 55.5 ms | 147.7 ms | 281.6 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.46 blocks | 0.41 blocks | 0.45 blocks |
| Rate limited | 0 | 35 | 1,362 |
| Unsupported | 0 | 0 | 17 |
| Samples | 8,364 | 8,356 | 1,991 |
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.7points
- Latency+15.8
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +15.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+21.4points
- Latency+21.5
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +21.4, exactly — the score is a weighted sum, so it comes apart.