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 00:42:35 UTC
| Metric | Tenderly | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 5 | 6 | 8 |
| Score | 99.4 | 83.7 | 78.0 | 59.4 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 100.00% | 99.97% | 100.00% | 77.78% |
| p50 latency | 18.2 ms | 105.4 ms | 106.6 ms | 1326.0 ms |
| p95 latency | 31.7 ms | 122.2 ms | 190.5 ms | 7406.7 ms |
| p99 latency | 53.9 ms | 150.1 ms | 278.7 ms | 9776.0 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 96.96% |
| Head lag | 0.46 blocks | 0.41 blocks | 0.52 blocks | 0.94 blocks |
| Rate limited | 0 | 28 | 1,521 | 1,564 |
| Unsupported | 0 | 0 | 17 | 0 |
| Samples | 9,255 | 9,237 | 2,226 | 2,151 |
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
+15.8points
- Latency+15.8
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +15.8, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+21.4points
- Latency+21.3
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.4, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+40.0points
- Latency+30.0
- Availability+8.9
- Correctness+0.6
- Head freshness+0.5
The parts add to +40.0, exactly — the score is a weighted sum, so it comes apart.