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
1h window · 60 minutes observed · generated 2026-08-28 00:43:04 UTC
| Metric | Tenderly | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 5 | 6 | 8 |
| Score | 99.1 | 83.9 | 77.7 | 60.3 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 100.00% | 100.00% | 100.00% | 79.94% |
| p50 latency | 17.1 ms | 103.4 ms | 102.0 ms | 1326.0 ms |
| p95 latency | 30.5 ms | 117.4 ms | 202.2 ms | 7406.7 ms |
| p99 latency | 53.5 ms | 146.5 ms | 316.7 ms | 9776.0 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 96.96% |
| Head lag | 0.48 blocks | 0.41 blocks | 0.40 blocks | 0.94 blocks |
| Rate limited | 0 | 13 | 253 | 246 |
| Unsupported | 0 | 0 | 2 | 0 |
| Samples | 1,596 | 1,594 | 356 | 632 |
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.3points
- Latency+15.3
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +15.3, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+21.4points
- Latency+21.5
- 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
+38.9points
- Latency+29.7
- Availability+8.0
- Correctness+0.6
- Head freshness+0.5
The parts add to +38.9, exactly — the score is a weighted sum, so it comes apart.