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 17:15:02 UTC
| Metric | Tenderly | Blast API | Merkle |
|---|---|---|---|
| Rank | 1 | 5 | 6 |
| Score | 99.4 | 78.1 | 69.5 |
| Status | Excellent | Good | Degraded |
| Availability | 99.99% | 99.98% | 100.00% |
| p50 latency | 19.9 ms | 108.5 ms | 110.9 ms |
| p95 latency | 33.9 ms | 125.6 ms | 207.7 ms |
| p99 latency | 84.0 ms | 142.8 ms | 293.9 ms |
| Correctness | 99.99% | 99.98% | 100.00% |
| Head lag | 0.51 blocks | 0.40 blocks | 0.46 blocks |
| Rate limited | 0 | 1 | 1,371 |
| Unsupported | 0 | 0 | 15 |
| Samples | 8,526 | 8,508 | 1,969 |
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
+21.2points
- Latency+21.4
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.2, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+29.8points
- Latency+29.9
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +29.8, exactly — the score is a weighted sum, so it comes apart.