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
24h window · 24 hours observed · generated 2026-08-26 23:42:30 UTC
| Metric | Tenderly | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 5 | 6 | 8 |
| Score | 98.9 | 84.1 | 78.0 | 64.1 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.97% | 99.98% | 100.00% | 89.01% |
| p50 latency | 19.8 ms | 104.3 ms | 107.0 ms | 259.6 ms |
| p95 latency | 37.4 ms | 121.0 ms | 195.7 ms | 2579.7 ms |
| p99 latency | 251.5 ms | 140.5 ms | 240.0 ms | 4625.5 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 98.18% |
| Head lag | 0.49 blocks | 0.42 blocks | 0.46 blocks | 0.94 blocks |
| Rate limited | 0 | 371 | 6,157 | 6,579 |
| Unsupported | 0 | 0 | 80 | 0 |
| Samples | 38,415 | 38,186 | 8,873 | 7,878 |
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.7points
- Latency+14.8
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +14.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+20.8points
- Latency+20.9
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +20.8, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+34.7points
- Latency+29.5
- Availability+4.4
- Head freshness+0.5
- Correctness+0.4
The parts add to +34.7, exactly — the score is a weighted sum, so it comes apart.