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-27 02:53:32 UTC
| Metric | Tenderly | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 5 | 6 | 8 |
| Score | 99.1 | 84.1 | 78.0 | 58.5 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.98% | 99.98% | 100.00% | 75.73% |
| p50 latency | 19.7 ms | 104.5 ms | 107.1 ms | 2024.4 ms |
| p95 latency | 36.6 ms | 121.1 ms | 195.3 ms | 6590.4 ms |
| p99 latency | 207.2 ms | 141.0 ms | 239.0 ms | 9196.2 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 96.63% |
| Head lag | 0.49 blocks | 0.42 blocks | 0.46 blocks | 0.95 blocks |
| Rate limited | 0 | 285 | 6,216 | 6,634 |
| Unsupported | 0 | 0 | 82 | 0 |
| Samples | 38,702 | 38,484 | 8,905 | 7,957 |
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.0points
- Latency+15.1
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +15.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+21.1points
- Latency+21.2
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +21.1, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+40.6points
- Latency+29.7
- Availability+9.7
- Correctness+0.7
- Head freshness+0.5
The parts add to +40.6, exactly — the score is a weighted sum, so it comes apart.