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 23:11:35 UTC
| Metric | Tenderly | Blast API | Merkle |
|---|---|---|---|
| Rank | 1 | 5 | 6 |
| Score | 99.4 | 78.3 | 71.0 |
| Status | Excellent | Good | Degraded |
| Availability | 100.00% | 99.91% | 100.00% |
| p50 latency | 18.7 ms | 106.8 ms | 107.9 ms |
| p95 latency | 32.2 ms | 124.1 ms | 187.6 ms |
| p99 latency | 54.0 ms | 152.1 ms | 236.0 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.47 blocks | 0.41 blocks | 0.53 blocks |
| Rate limited | 0 | 44 | 1,363 |
| Unsupported | 0 | 0 | 12 |
| Samples | 8,409 | 8,411 | 2,026 |
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.2
- 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
+28.4points
- Latency+28.4
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +28.4, exactly — the score is a weighted sum, so it comes apart.