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 22:17:32 UTC
| Metric | Tenderly | Blast API | Merkle |
|---|---|---|---|
| Rank | 1 | 5 | 6 |
| Score | 99.4 | 78.1 | 69.9 |
| Status | Excellent | Good | Degraded |
| Availability | 99.99% | 99.99% | 100.00% |
| p50 latency | 18.8 ms | 107.3 ms | 108.2 ms |
| p95 latency | 33.2 ms | 123.5 ms | 201.2 ms |
| p99 latency | 64.7 ms | 139.8 ms | 241.7 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.43 blocks | 0.46 blocks |
| Rate limited | 0 | 6 | 1,366 |
| Unsupported | 0 | 0 | 13 |
| Samples | 8,588 | 8,578 | 1,989 |
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.3points
- Latency+21.3
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.3, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+29.5points
- Latency+29.5
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +29.5, exactly — the score is a weighted sum, so it comes apart.