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
7d window · 2.1 days observed · generated 2026-08-26 22:25:03 UTC
| Metric | Tenderly | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 5 | 6 | 8 |
| Score | 91.2 | 85.8 | 78.7 | 63.8 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.96% | 99.98% | 99.98% | 88.36% |
| p50 latency | 20.0 ms | 104.7 ms | 106.7 ms | 189.3 ms |
| p95 latency | 84.8 ms | 122.6 ms | 196.4 ms | 2922.0 ms |
| p99 latency | 914.7 ms | 145.1 ms | 244.4 ms | 6561.8 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 97.72% |
| Head lag | 0.51 blocks | 0.42 blocks | 0.47 blocks | 0.90 blocks |
| Rate limited | 0 | 915 | 13,007 | 13,850 |
| Unsupported | 0 | 0 | 159 | 0 |
| Samples | 80,641 | 80,122 | 18,741 | 16,916 |
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
+5.4points
- Latency+5.5
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +5.4, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+12.6points
- Latency+12.6
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +12.6, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+27.4points
- Latency+21.9
- Availability+4.6
- Correctness+0.5
- Head freshness+0.4
The parts add to +27.4, exactly — the score is a weighted sum, so it comes apart.