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-28 00:43:29 UTC
| Metric | Tenderly | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 5 | 6 | 8 |
| Score | 99.4 | 83.8 | 78.0 | 58.7 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.98% | 99.97% | 100.00% | 75.93% |
| p50 latency | 19.2 ms | 106.2 ms | 107.4 ms | 1326.0 ms |
| p95 latency | 32.9 ms | 123.4 ms | 193.1 ms | 7406.7 ms |
| p99 latency | 69.6 ms | 151.0 ms | 256.1 ms | 9776.0 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 96.96% |
| Head lag | 0.47 blocks | 0.41 blocks | 0.52 blocks | 0.94 blocks |
| Rate limited | 0 | 283 | 6,134 | 6,596 |
| Unsupported | 0 | 0 | 75 | 0 |
| Samples | 38,444 | 38,419 | 8,950 | 7,914 |
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.6points
- Latency+15.6
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +15.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+21.4points
- Latency+21.4
- 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.8points
- Latency+30.0
- Availability+9.6
- Correctness+0.6
- Head freshness+0.5
The parts add to +40.8, exactly — the score is a weighted sum, so it comes apart.