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
30d window · 4.1 days observed · generated 2026-08-28 23:16:21 UTC
| Metric | Tenderly | Blast API | Merkle |
|---|---|---|---|
| Rank | 2 | 5 | 6 |
| Score | 98.6 | 84.1 | 78.0 |
| Status | Excellent | Good | Good |
| Availability | 99.97% | 99.98% | 99.99% |
| p50 latency | 19.6 ms | 105.2 ms | 107.0 ms |
| p95 latency | 39.6 ms | 122.4 ms | 196.0 ms |
| p99 latency | 539.4 ms | 146.5 ms | 243.9 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.42 blocks | 0.49 blocks |
| Rate limited | 0 | 1,564 | 25,664 |
| Unsupported | 0 | 0 | 307 |
| Samples | 159,823 | 159,217 | 37,060 |
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
+14.5points
- Latency+14.5
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +14.5, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+20.6points
- Latency+20.6
- Availability−0.0
- Head freshness−0.0
- Correctness−0.0
The parts add to +20.6, exactly — the score is a weighted sum, so it comes apart.