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
1h window · 60 minutes observed · generated 2026-08-28 22:18:21 UTC
| Metric | Tenderly | Blast API | Merkle |
|---|---|---|---|
| Rank | 1 | 5 | 7 |
| Score | 99.4 | 78.2 | 69.4 |
| Status | Excellent | Good | Degraded |
| Availability | 100.00% | 100.00% | 100.00% |
| p50 latency | 18.0 ms | 105.6 ms | 106.2 ms |
| p95 latency | 31.5 ms | 120.1 ms | 206.7 ms |
| p99 latency | 64.0 ms | 139.0 ms | 231.6 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.45 blocks | 0.53 blocks |
| Rate limited | 0 | 4 | 255 |
| Unsupported | 0 | 0 | 1 |
| Samples | 1,606 | 1,591 | 377 |
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.3
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +21.2, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+30.1points
- Latency+30.0
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +30.1, exactly — the score is a weighted sum, so it comes apart.