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 · 2.7 days observed · generated 2026-08-27 12:59:24 UTC
| Metric | Tenderly | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 5 | 6 | 8 |
| Score | 95.8 | 85.1 | 78.5 | 62.4 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.96% | 99.98% | 99.98% | 84.99% |
| p50 latency | 19.8 ms | 104.8 ms | 106.5 ms | 225.7 ms |
| p95 latency | 55.1 ms | 122.2 ms | 196.3 ms | 4391.3 ms |
| p99 latency | 787.0 ms | 146.1 ms | 243.5 ms | 7602.5 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 97.48% |
| Head lag | 0.50 blocks | 0.42 blocks | 0.48 blocks | 0.91 blocks |
| Rate limited | 0 | 1,154 | 16,763 | 17,891 |
| Unsupported | 0 | 0 | 203 | 0 |
| Samples | 104,233 | 103,662 | 24,151 | 21,906 |
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
+10.8points
- Latency+10.9
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +10.8, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+17.3points
- Latency+17.3
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +17.3, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+33.4points
- Latency+26.4
- Availability+6.0
- Correctness+0.5
- Head freshness+0.5
The parts add to +33.4, exactly — the score is a weighted sum, so it comes apart.