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 20:44:58 UTC
| Metric | Tenderly | Blast API | Merkle |
|---|---|---|---|
| Rank | 1 | 5 | 6 |
| Score | 99.4 | 78.4 | 70.7 |
| Status | Excellent | Good | Degraded |
| Availability | 99.99% | 99.92% | 100.00% |
| p50 latency | 19.5 ms | 108.9 ms | 110.1 ms |
| p95 latency | 32.9 ms | 127.4 ms | 192.2 ms |
| p99 latency | 57.9 ms | 154.6 ms | 236.0 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.41 blocks | 0.61 blocks |
| Rate limited | 0 | 67 | 1,487 |
| Unsupported | 0 | 0 | 18 |
| Samples | 9,313 | 9,303 | 2,207 |
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.0points
- Latency+21.1
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +21.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+28.7points
- Latency+28.5
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +28.7, exactly — the score is a weighted sum, so it comes apart.